RE: [PEAR-DEV] [PEAR|M]DB : Sql Parser / Requirements for a Rewrite Engine
| From: | Lukas Smith | Date: | Thu, 15 May 2003 14:31:35 +0000 |
| Subject: | RE: [PEAR-DEV] [PEAR|M]DB : Sql Parser / Requirements for a Rewrite Engine | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-16302@lists.php.net to get a copy of this message | ||
> From: l0t3k [mailto:cshmoove@bellsouth.net]
> Sent: Thursday, May 15, 2003 4:26 PM
> if im not mistaken, there have been discussions about rudimentary SQL
> rewriting to emulate missing/differently implemented backend features.
> assuming a (semi) capable generic SQL parser, what would be necessary
to
> support the rewriting engine ?
>
> im toying with a SQL parser extension (don't get excited yet) and im
> trying
> to figure how to make it useful in user-space.
Well I was just talking with Zak this morning about something like this.
And our conclusion was that there are probably methods to do generic
query optimizations and rewriting using an SQL Parser. I really don't
know if this really makes sense though.
In terms of integration I would simply make this optional drivers for
[M]DB.
For example:
MDB today:
MDB_mysql extends MDB_Common
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