> > > 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...
>
> Personally I think this is brittle. If there's good use for it I won't
> object but it doesn't have my preference.
or a $object->type for instance
if i want to add parameters to every object however the parameters differ
according to the object type such as host, article etc i would do
function addparameter($object)
{
if ($object->type=="host")
add some parameter
elseif ($object->type=="article")
add some other parameter
}
just an example....
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
