Re: [PEAR|M]DB : Sql Parser / Requirements for a Rewrite Engine
| From: | l0t3k | Date: | Thu, 15 May 2003 16:09:00 +0000 |
| Subject: | Re: [PEAR|M]DB : Sql Parser / Requirements for a Rewrite Engine | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-16308@lists.php.net to get a copy of this message | ||
Lukas,
actually what i was thinking about was this :
say we have a "portability" mode for MDB. in this mode all queries are
written in our "dialect", which is just a generic ANSI subset along with
syntax for our "non-standard" features. the best example is query limiting,
as every backend has a different way of specifying this..
in portability mode, each driver would use the SQL parser to parse the
user query and rewrite it to a form acceptable to the backend. in other
words, we would not need two sets of drivers, but a new flag to state
whether or not the driver supports rewriting in portability mode.
l0t3k
"Lukas Smith" <smith@backendmedia.com> wrote in message
news:003c01c31aee$b12beb50$4d00a8c0@vandal...
> > From: l0t3k [mailto:cshmoove@bellsouth.net]
> > Sent: Thursday, May 15, 2003 4:26 PM
> MDB with alternative sql rewriter
> MDB_mysql extends MDB_Rewriter extends MDB_Common
>
> So there would infact be two different implementations of MDB_mysql.
> Probably the root of all evils in every softwaredesign book.
>
> Regards,
> Lukas
>