Re: [Dbmail-dev] dbmail 2.0.0 w/ mysql 4.1.7 borked?

2004-10-28 Thread Mikhail Ramendik
Aaron Stone wrote: > We should make this change in CVS for both HEAD and dbmail_2_0_branch and > put a note on the website that 2.0.0 may have compatibility issues with > MySQL 4.1.x. Is there a cvs dbmail_2_0_branch already? If so, I'd really like to know the decision on including my patches. Th

Re: [Dbmail-dev] dbmail 2.0.0 w/ mysql 4.1.7 borked?

2004-10-28 Thread Aaron Stone
Mikhail Ramendik <[EMAIL PROTECTED]> said: > Alternatively just search that file for "db_real_query", because that's > the call where it does the <0 check, and change the check there to !=0 . We should make this change in CVS for both HEAD and dbmail_2_0_branch and put a note on the website that

Re: [Dbmail-dev] dbmail 2.0.0 w/ mysql 4.1.7 borked?

2004-10-28 Thread Mikhail Ramendik
Bernard Johnson wrote: > Incompatible change: TIMESTAMP is now returned as a string in > '-MM-DD HH:MM:SS' format (from 4.0.12 the --new option can be used to > make a 4.0 server behave as 4.1 in this respect). See section 12.3.1.2 > TIMESTAMP Properties as of MySQL 4.1. If you want to have th

[Dbmail-dev] dbmail 2.0.0 w/ mysql 4.1.7 borked?

2004-10-28 Thread Bernard Johnson
Seeing that mysql 4.1.7 is now "GA", I started looking into upgrading a couple of servers. I took some time to read through the release notes (http://dev.mysql.com/doc/mysql/en/Upgrading-from-4.0.html), and I found two things that looked like they might cause some fits with dbmail 2.0.0. Can some