Re: one abstraction layer (my proposal for)
| From: | l0t3k | Date: | Sun, 02 Dec 2001 15:06:42 +0000 |
| Subject: | Re: one abstraction layer (my proposal for) | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3291@lists.php.net to get a copy of this message | ||
Lukas
> > 4.3) Secuencial & Non Secuencial Row Fetching
> just a question: whats the purpose of non sequencial row fetching?
> Aside from legacy support is there really a need for this?
> Most people on this list said the don't use it.
> This is important to figure out for what is core and what should be
> loaded on demand.
>
one thing we are forgetting is that PHP is now more than a web app tool. You
can see the possibilities by looking at PHP-GTK. im not suggesting that we
be all things to all people, but that should be kept in mind. i raise this
because there are already folks creating database management tools for GTK
using PHP (AGATA i think is the project name) and i think they may need
something like this. but in cases like these, extended functions can be made
non-core.
> > 4.13) Results cache
> (as a side note: I would want any thing that serializes to be cluster
> capable. I am also currently working on data containers where I can
> throw parameters into the db to be used later. Like when I have a
> preview etc. Nothing special but I need this for files and passwords
> that you don't want/cant place in a hidden field)
im not sure i understand this one. you mean something thats mime encoded or
otherwise encodes data that may cause issues ?
l0t3k