Re: Re: Datagrid and linking dataobjects
| From: | Larry Garfield | Date: | Thu, 20 Jan 2005 22:37:07 +0000 |
| Subject: | Re: Re: Datagrid and linking dataobjects | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-17059@lists.php.net to get a copy of this message | ||
Justin Patrin wrote:
Ah. Well, the ini file hasn't changed since I ran createTables.php, nor have I moved any classes, yet it's still not working. I just put in an "include_once() everything in this directory" block, and that's working fine for me. (Maybe costs a few cycles, but I don't think enough to worry about.) So I'll just be happy with new for now. :-) -- Larry Garfield AIM: LOLG42 larry@garfieldtech.com ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas JeffersonThe main advantage is not having to require_once() all of yout DO class files. If you get a class not found error there's probably a problem with your ini file or the way that you're loading it for your scripts.OT: *Why* does everyone use new with DataObjects? Why not use DB_DataObject::factory()?In my case, because for unknown reasons I get a class not found error returned whenever I use factory() but new works fine. And I've not yet figured out what if anything is the advantage of using one over the other. :-) What is the advantage of using factory() instead of new anyway?