Zikula Community

• Topiatic
  
  

  • Rank: Expert
  • Registered: Nov 23, 2003
  • Last visit: Dec 13, 2009
  • Posts: 1487

  Posted: Oct 03, 2007 - 05:41 AM

  From this post: http://community.pos…pic-topic-53102.htm
  
  Cool!!!
  
  But I just can't figure out what the origional $obj is supposed to be. The ObjUtil class simply says "@param object The object whose attribute we wish to...". Is this supposed to be the actuall table object as gotten from DBUtil::selectObjectArray() for the table the attributes belong to? Or the calling modules resulting object? Or what?
  
  Any help here would be greatly appreciated.
  
  --
  Under Construction!

  • 
  •  
• Guite
  
  

  • Rank: Team Member
  • Registered: Jan 19, 2003
  • Last visit: Apr 06, 2010
  • Posts: 442

  Posted: Oct 03, 2007 - 08:02 AM

  If you want to use attributes you want to enhance existing objects with additional information without having to manipulate their database scheme. So if you for example add new fields to a user, then the object is a result of a DBUtil method selecting an entry from the users table.
  The reason behind this approach is that any object enhancements (like attributes, metadata, categories, ASO) are handled centrally in DBUtil when the object is being updated itself. So a DBUtil method needs any extensions as a subarray within the object passed to it.
  
  --
  Guite | ModuleStudio

  • 
  •  
• rgasch
  
  

  • Rank: Team Member
  • Registered: Jan 05, 2003
  • Last visit: May 28, 2010
  • Posts: 775

  Posted: Oct 03, 2007 - 08:45 AM

  Hi,
  
  $obj is a (either single or array of data arrays) associative data array returned from DBUtil::selectObjectArray(). ObjectUtil will deal with it accordingly ... ObjectUtil alters the object in place so the stuff is automagically added to the object you pass in.
  
  Greetings
  R

  • 
  •  
•  
•  

Users on-line

• 0 users

This list is based on users active over the last 60 minutes.