Re: Bug in 3.0.16 with Mysql-4.1.7 ?
Posted by: Mark Matthews
Date: November 22, 2004 07:43PM

I'll file this as a bug tomorrow so it will get tracked, and fixed. We'll have to do some internal discussion to see if it can be fixed in the 3.0 branch or not, since 3.1.x is about to go stable, and it is the version that people 'really' should be using with MySQL-4.1 (3.0.x only promises 'limited' functionality with 4.1.x).

Options: ReplyQuote

Written By
November 18, 2004 09:21PM
Re: Bug in 3.0.16 with Mysql-4.1.7 ?
November 22, 2004 07:43PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.