Odp: Re[3]: [PHP-DB] Re: MySql or postgre?

Od: "Alexey Borzov" <borz_off@rdw.ru> Temat: Re[3]: [PHP-DB] Re: MySql or postgre? > There is only one side of the question: > _If_ MySQL is a standards-compliant RDBMS then transactions are a vital part > of it (read the SQL standard) and should be implemented in the core > engine (as my quite limited programming experience tells me), not as > "second party addons". If it is not - then be _honest_ about it, > drop that annoying 'SQL' part, rename it to something like > My-Flat-File-DB-with-SQL-like-interface. And stop comparing it with > _real_ RDBMS's (be it Interbase, Postgres or Oracle). > The problem is that most of MySQL's users are not knowledgeable enough to > understand its limits, and MySQL's developers and advocates are > sometimes reluctant to admit them... They only talk 'speed'... Men, i was dying from laugh when i readed their "benchmark" information... In db-programmers community there are many similar "benchmarks", which compare FoxPro with solid nature of Interbase. Many people believe in all these absurds and ask: "hey, why the IB is so slow?!". My only answer is: "If i go to war, i choose Leopard 2A5 or Leclerc - not Ferrari, i choose BMP-3 - not Iveco truck, 'cause i will fight and question if i survive is vital to me, not to be fast". In fact, comparing file ("desktop") database with real SQL-compliant database server is like comparing car with tank and - believe me - programming is like war... If you really want to compare "speed", do not use any front-ends, only embedded (built-in) capabilities like stored procedures (didn't see anything like that in MySQL), referential integrity ("why do not use RI?"), triggered actions (i.e. ON UPDATE|ON DELETE CASCADE|DELETE|SET NULL|NO ACTION), triggers (BEFORE|AFTER DELETE|UPDATE|INSERT), custom exceptions, linked UDF's, two-phase commit, constraints etc. How many of them are present in MySQL? I can say with hand on my heart, that since i started working with Interbase i do not want any DBMS that doesn't provide me these things. Really, MySQL is very good database compared to dBase, Paradox, FoxPro or even Access, but it's not a match for any real database server. Do not mix them! Cheers Jarek Zgoda