MySQL Bugs: #17558: generic API wanted

Bug #17558	generic API wanted
Submitted:	19 Feb 2006 18:01	Modified:	15 Apr 2006 2:06
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S4 (Feature request)
Version:	any	OS:	Any (any)
Assigned to:		CPU Architecture:	Any

Description:
First I must apologize if this is the wrong category!

Following the release by MySQL AB of PHP-connectors (and a lot of writing and confusion with this in all sorts of Forums and mailing-lists around the world) I shall suggest the MySQL AB releases and maintains a 'generic' C-API that can be compiled into any client. (connectors, graphical clients (by MYSQL AB and third party vendors).  Such 'generic API'  should identify the server version and adjust to each major MySQL version still supported.

We are a lot of people connecting to the most varied set of MySQL server versions. Supporters, consultants, application developers etc. .  Sometimes we even need to have connections open to more (different) servers at the same time with the same client.  

How to repeat:
Not relevant here!

Suggested fix:
generic API wanted! :-)

Please, take a look at existing C API (http://dev.mysql.com/doc/refman/5.0/en/c.html). Isn't it the very thing you asked for?

Well, not if I read and understand this http://dev.mysql.com/downloads/connector/php/ correctly.  I must understand this as if connection to every specific server version should be done with a client libraryy specific for that server version.  This is impracticable in the situations when you will need to connect to a lot of servers.  I need to connect to twelve.  Plus some test setups of my own.  Should I ask every vendor creating client software to provide me with a version of each?

What do you think Volvo would say if you asked them to provide specific instrumentation in their cars for each different type of roads? :-)

I request an API that 'branch'es between code-variants so that it will work 100%with ANY still-supported MySQL version.

I must add that I personally have add any kind of problem with any client, no matter which API-version is was compiled with, that could be related to this.  But as new MySQL versions come up an old ones are still supported, I fear that it will not continue to be so.

please change my garbage to: 

I must add that I personally have not had any kind of problem with any
client, no matter which API-version is was compiled with, that could be
related to this.

All versions of the client library maintain backwards compatibility to previous server versions, so if you e.g. use the 5.0 client library then you can connect to and work with 5.0, 4.x and 3.23 servers just fine (unless you try to use e.g. a 5.0 feature on a 3.23 server).