Re: Migrate from MySQL to PostgreSQL

Hi Alexey! Alexey Borzov wrote: > 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? 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? > The approach you described makes you code for the lowest common > denominator and just use the database as an extremely stupid data > store. Could be, but it works nice and I save a lot of work now, and for maintaining in the futere. So if I do what you suggest, the application would became more expensive, and doens't perform noticable better. So why should I do this? regards, Andreas