Re: Migrate from MySQL to PostgreSQL
| From: | Alexey Borzov | Date: | Fri, 23 Jan 2004 14:37:13 +0000 |
| Subject: | Re: Migrate from MySQL to PostgreSQL | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-10331@lists.php.net to get a copy of this message | ||
Hi!
Andreas Korthaus wrote:
I am not *forcing* you to swith to this. I just wanted to point out another possible approach that will help you use all the power of the supported databases.I suggest rethinking your approach then and write a separate database access layer for each database engine. This layer will contain all the SQL needed to interact with the database and you will just call PHP functions from everywhere else. The layer for MySQL will contain a lot of ugly PHP code while the layer for a more advanced RDBMS just some procedure calls.Hm, but If I don't have problems with performance or data integrity - WHY? Only to USE the Featurs?
I use transactions, so what should be the problem?Transactions are not magic, you can still have transactions *and* inconsistent data.
I don't know the exact number, but I think I have something between 150-300 queries. And I want to support at least 5 different RDBMS. So this would be a tremendous work - what for? What should be the benefit?Scalability. Though I agree, it will take more work to support multiple databases this way.