Re: DB portability
| From: | Daniel Convissor | Date: | Tue, 02 Jan 2001 23:28:18 +0000 |
| Subject: | Re: DB portability | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-32425@lists.php.net to get a copy of this message | ||
Hi Nathan:
> I am looking at undertaking a very large project that will be handled
> initially in MySQL. Down the road we may choose a corporate db such as
> Oracle. My thought was since we will have thousands of lines of code to
> migrate to the new db, I could create a global script that is required by
> each individual script.
> ...
>
> Can any of you see any repercussions of this central database alias script?
There are powerful pluses, as you've already realized. Coding pages is far
quicker, plus the code is portable.
The downside is minor, adding a bit of overhead, but it's worth it, in my
book.
I have a piece of software, SQL Solution, that does this for MySQL and ODBC
databases already. Check it out at
http://www.analysisandsolutions.com/code/sql/.
You can go ahead and use it
as is (or extract the parts you like) and if the need arises to move to
another database, you can port it.
Manuel Lemos has a good set of database classes, named Interbase, as well:
http://phpclasses.UpperDesign.com/?user=mlemos@acm.org
Enjoy,
--Dan
--
PHP scripts that make your job easier
http://www.analysisandsolutions.com/code/
SQL Solution | Layout Solution | Form Solution
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
4015 7 Ave, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409