You have a good point...but the reason for MySQL 4.1 is because it allows subqueries that are required for other software running through that server.
I don't particularly like running alpha software, but I have been using MySQL for years and they have always proven to be stable for me even in the alpha and beta stages. I'll follow your suggestions and can always backup to 1.2.7 (or 1.2.6 as that's the one that actually compiled correctly before I updated to the later version of MySQL). Thanks. > On Sun, 2004-05-02 at 20:41, John M. Brown wrote: >> Got another problem when trying to add the line. >> >> Here's the error: >> In file included from /usr/include/mysql/mysql.h:64, >> from mysql/dbmysql.c:12: >> /usr/include/mysql/my_list.h:34: conflicting types for `list_reverse' >> list.h:43: previous declaration of `list_reverse' >> make: *** [mysql/dbmysql.o] Error 1 >> Sorry, Make failed. >> Please report any problems to the mailing list: dbmail@dbmail.org >> > This is because of a function with the same name (list_reverse) that > MySQL exports.. > > MySQL 4.0 does not export this function, AFAIK >> Upgrading to 1.2.7 version with MySQL 4.1 (latest) >> >> It compiles fine under 2.0rc4...but I can't use a release candidate on a >> production server. Any idea when 2.0 will be production ready? >> > Just out of curiosity: Why not run a release candidate when you do run > alpha software (MySQL 4.1)? > > Ilja > > > _______________________________________________ > Dbmail mailing list > Dbmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail >
