Re: Re: [PEPr] Comment on Tools and Utilities::DbDeploy
| From: | Luke Crouch | Date: | Mon, 17 Sep 2007 18:24:11 +0000 |
| Subject: | Re: Re: [PEPr] Comment on Tools and Utilities::DbDeploy | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-48032@lists.php.net to get a copy of this message | ||
it utilizes the new PDO extension and those drivers for db connection
abstraction, so you can connect to any db platform via a connection DSN in
the config file.
but it doesn't use MDB or any other fuller db abstraction for the
data-types. I wrote the syntax objects into it merely because I think it
only deals with 1 data type abstraction - DbDeploy doesn't actually perform
the schema changes. the only time it connects to the database is to check
the schema's version via the changelog table. so really, DbDeploy only ever
operates on that single table, and that table has only 1 column of an "odd"
data type (timestamp field). so I thought adding on full-out db abstraction
for that 1 field might be overkill and give it a frivolous dependency.
so it uses PDO & PDO drivers installed into PHP 5+, but does not use the
other PEAR DB packages.
-L
On 9/17/07, till <till@php.net> wrote:
>
> Hi Luke,
>
> thanks for elaborating. I see the light^H^H^H^differences. :-)
>
> On 9/17/07, Luke Crouch <luke.crouch@gmail.com> wrote:
> > (...)
> > * No MDB2 dependency - in fact, no DB abstraction at all. this can be
> both
> > positive and negative - positive in the sense that if you are working on
> a
> > project in which you have full control over the DB platform (as is the
> case
> > in many website projects), you can directly use platform-specific SQL
> > dialect and features in your db schema changes.
>
> I forgot to add this to my initial comment. IMO it would be nice if it
> used existing code because you wouldn't need to maintain a dozen
> drivers - again.
>
> > (...)
>
> Till
>