Re: MySQLi Compat question

John Coggeshall wrote:

On Mon, 2003-06-09 at 18:50, Rasmus Lerdorf wrote: Are you suggesting that there be a single ext/mysql which has mysql_connect() as well as mysqli_connect()? I ask because I know what your describing in terms of the end result, but I'm not clear on how it would be implemented.. I guess you could "merge" ext/mysql and ext/mysqli into a single extension, but then you've got half the mysql functions which require a link parameter, half which don't.. I'm a bit tired right now, but that by itself seems more confusing than having two separate extensions for the two versions. Instead of getting 500 "Which MySQL extension should I use?" it seems you'd get "Which connect() function do I use??" and "Why can't I use mysql_connect()? I'm running 4.1..." among others. Or is there a clean implementation I don't see? Does the old 3.x client play nicely with 4.1 servers? I haven't tested that. Even if it doesn't that only temporarily mask the license issue? Eventually, it'd be really nice to be able to take advantage of 4.1+ things in PHP and if that's the case now seems like an ideal time to address it. - John

The problem is that the MySQL 3.x API and 4.0 API are compatible, and you can use the 3.x client with MySQL 4.0, However - heres the tricky part where people are getting lost - the MySQL 3.x (and 4.0) API are NOT compatible with MySQL 4.1 - Ideally, I think they should have waited till 5.0 before doing an API change.. much less confusing for everyone concerned. - Davey