Le Jeudi 04 Mai 2006 09:51, [EMAIL PROTECTED] a écrit : > Hello, Hi,
> I must say, I find very deceptive the way you "fixed" this bug by removing > mysql support :( I gave you all the infos to correct this and you didn't. > You just had to read Mysql 5 documentation to understand how to solve it, > and you choosed a lamer's way ! Bravo ! You may want to know a little more than you do about rdbms support in TUTOS and the way it evolved in the BRANCH-2-0. This project began with support for as many rdbm as you want to support, the way it is usually done : the written (generated) SQL command can be sent by using any protocol/library, then the resultset is parsed and its format is adapted for further usage. The problem with this way of supporting several RDBM is that the written request is written once for all of them, hence for example if you support MySQL (previous its version 5) you then can't write any subqueries in your SQL. When I was paid to develop TUTOS 2 branch, we made the choice to only support PostgreSQL, our RDBM of choice. And I wrote some complex queries involving a syntax MySQL wouldn't be able to understand. The MySQL support in TUTOS was from there broken, but I forgot to mark this in the debian package. Our way to resolve the debian bug was to effectively mark tutos as being a PostgreSQL only project, a decision taken two years ago. Hoping this answer will help you understand the choices, regards, -- Dimitri Fontaine http://dim.tapoueh.org
pgpkPaUlXzV4r.pgp
Description: PGP signature
