Re: Re: DB_DataObject joinAdd
| From: | Justin Patrin | Date: | Thu, 24 Jun 2004 15:14:27 +0000 |
| Subject: | Re: Re: DB_DataObject joinAdd | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-13309@lists.php.net to get a copy of this message | ||
It has nothing to do with the new features. It's just a wasy to
distinguish the fields from the DB from options. Since this is an
encapsulating object, it needs such a difference.
On Thu, 24 Jun 2004 10:13:30 +0200, Bertrand Mansion
<bmansion@mamasam.com> wrote:
>
>
> Justin Patrin wrote:
>
> >On Thu, 24 Jun 2004 08:19:39 +0800, Alan Knowles <alan@akbkhome.com> wrote:
> >> Daniel Kopp wrote:
> >> > Alan Knowles wrote:
> >> > which seems to work even though I am pretty sure it will break in
> >> > php5 (there is protected mode for object-properties in php5 isn't
> >> > it?)
> >>
> >> DataObjects is a little odd in some respects, all the public (eg. non
> >> _prefixed vars) are assumed to be available to be used as column names)
> >> - so all other variables end up with _underscores, even though their
> >> protection level may be public as well..
> >>
> >
> >We're running into this with FormBuilder as well. We're planning on
> >using fb_varName for FormBuilder options in the DataObject.
>
> That's another example where the underscore looks stupid in regard to the new
> features provided by PHP, don't you think ?
>
> Bertrand Mansion
> Mamasam
>
>
--
paperCrane --Justin Patrin--