Re: [PROPOSAL] DB_Simple

From: Date: Tue, 11 Nov 2003 14:57:49 +0000
Subject: Re: [PROPOSAL] DB_Simple
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-23442@lists.php.net to get a copy of this message
Hey, Alan,
OK: how about a detailed explanation for a brand-new user on how to extend DataObject both with a .ini file, compared with how to do it >> by embedding the .ini data within the class. Which properties control what? How does one build a calculated column?
This should cover most of this now. http://devel.akbkhome.com/livedocs/livedoc.php?q=package.database.db-dataobject.intro-autobuilding#package.database.db-dataobject.intro-autobuilding
Dude, *much* better. Thanks. :-)
How does one build multiple queries to be used within the class to retrieve different columns of data? Explicit instructions and examples.
This has been retitled, and should give the idea pretty quickly now. http://devel.akbkhome.com/livedocs/livedoc.php?q=package.database.db-dataobject.intro-filters#package.database.db-dataobject.intro-filters
Ew, problems. "Warning: sqlite_open(): database disk image is malformed in /var/svn_live/akpear/LiveDocs/livedoc.php on line 171"
Did I understand you to say the .ini file is autogenerated? (More doc suggestions follow.) Autogenerated from what? Can one hand-write the .ini file? Does one *have* to autogenerate a extension DataObject, or can hand-write the extended class? How does one autogenerate it anyway? How does one hand-write it? What are the strengths and weaknesses of each approach?
Alot of that is covered on the introduction on the retitled/updated page "Auto Building and Database Schema"
Same SQLite probs -- looking forward to reading it and the other; if it's as good as the autobuilding examples, I'll be a happy camper.
A spaceship filled with lawyers was sent into space and arrived on virgin planet earth. Unfortunatly they failed to invent the wheel, as they couldnt find any agreement on it. A spaceship filled with opensource developers was sent into space and arrived on virgin planet earth. They created 300 different wheels and 1/2 a million adapters so the wheels would work on differnt carts.. While natrual evolution is supposted to kill of the worst wheels, PEAR is attempting to sidestep evolution a little, and try and force the wheelmakers to work together.. (with mixed success :)
Ha! But as you say, "real" evolution would result in lots of dead wheels, with only the most well-adpated surviving the competition. I guess the PEAR sidestep is to not allow new wheels to compete against old ones. :-/ _______________________________________________________________________ Paul M. Jones Savant: the simple alternative to Smarty. http://phpsavant.com/

« previous php.pear.dev (#23442) next »