Emiliano wrote:

> David Guerizec wrote:
>> 3. create a new function that would fetch all the parameters (or all the
>> parameters in a domain) in an associative array on-demand.
>> 
>> The third solution is feasible now with the $midgard->types["object"] as
>> the first parameter of a generic function:
>> mgd_get_parameters($midgard->types["article"], $id [, $domain]);
> 
> 
> Why not a method on the object itself?
> 

or a method yes ;)

>> or even:
>> mgd_get_parameters($midgard->types[$obj->__table__], $obj->id [, $domain]);
> 
> 
> I would vote against this. The __table__ parameter is for internal use
> only
> and is virtually guaranteed to be gone with Midgard 2.0.

ok, what about a __type__ field then, containing the type or classname 
of object (ie. __type__="attachment" for __table__="blobs", etc.)

not necessary for this function/method, but for future enhancement...

> Emile



-- 
Best Regards,
David Guerizec           Free Software Developer
Aurora R&D               [EMAIL PROTECTED]
Midgard core developer   http://www.midgard-project.org/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to