Re: one abstraction layer (my proposal for)
| From: | Tomas V.V.Cox | Date: | Mon, 03 Dec 2001 01:06:54 +0000 |
| Subject: | Re: one abstraction layer (my proposal for) | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3305@lists.php.net to get a copy of this message | ||
Alexander Merz wrote:
>
> > > * (4.19) Support Nested Sets
> > Sorry, could you explain more that?
> "Nested Set" are a modell to work with trees stored in relational databases, at
> the moment i found only tutorials in german about this topic.
Ah ok. I know this under the name of "visitation model". Sincerely I
started a PEAR class to manage them but couldn't been able to make it
work as a general purpouse component (mostly because on how to fetch the
data in a query with joins or the lack of portable table LOCKs). We have
introduced parts of that for the pear web, so some code is actually
written for anyone wanting to do it :)
> > > > - This is just my attempt to see the "DB_One" class done
> > > Did you have only RDBMS in mind?
> > Actually yes. I find the idea of using files very limited as you can't
> > ensure file locks in multi-threads PHP sapi backends (that's the web).
> Not only files, i had object or xml-based dbms in mind.
Well, methods like connect, query or fetch are driver specific and could
be fit here when makes sense.
> Which layer should your proposal match?
A lightweight unified API plenty of helper methods to ensure
portability. Apply that to the layer you want, is the more I can say you
here Alex :)
Tomas V.V.Cox