Re: [phplib] database abstraction From: Bob Bowker (bowker <email protected>)
Date: 06/30/00

Jeff --

We went through the same thing with a client late last year ... the move
to a new database was made infinitely easier because (as is our
development habit) we had used a sys_procedures table to store every
query in the whole site. Not one line of production code was changed to
accommodate the new database - we did the whole thing by changing the
queries in sys_procedures, and changing the one class function which
read in the query requested by the page script.

Good luck!

Bob.

Jeff Kolber wrote:
>
> hi all,
>
> I am in a situation where I am developing webapp prototypes using mysql and
> just I learned that this will all eventually move over to oracle, but we
> don't know when the switch will be made.
>
> I am wondering if anyone can comment on using the database abstraction of
> phplib to easily allow me to continue developing using mysql and then
> switch to oracle without having to rewrite all my queries. I understand that
> there are more features in oracle and I'm probably going to want to rewrite
> some queries anyway. I am hoping that phplibs db abstraction will help save
> some time and effort in the switch. Has anyone who has done anything like
> this care to comment?
>
> thanks
>
> (I am not subscribed so please reply to me as well as the list)
>
> Jeff Kolber Director of Production
> IN2 | 205 Hudson Street, 7th Floor, New York, NY 10013
> jeff <email protected> | Phone 646-613-2007 | Fax 646-613-0648
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: phplib-unsubscribe <email protected>
> For additional commands, e-mail: phplib-help <email protected>

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>