MySQL Forums
Forum List  »  Connector/C++

Which features do you want for 1.1, 1.5, 2.0?
Posted by: Ulf Wendel
Date: May 06, 2009 02:13PM

Those who are interested in the development discussion on MySQL Connector/C++, please subscribe to the mailing list at . I do not know how you feel about forums, but my thinking is that they are traditionally best suited for ad-hoc questions. And mailing lists are perfect for development discussions. Let's move all development discussions onto the Connector/C++ ML.

1.0 GA is out. It has all features required to serve the "MySQL internal customers" Connector/ and MySQL Workbench. It is overdue to open up the development and ask "what do you want".

Here we go, please reply on the ML:


we have released Connector/C++ 1.0.5 GA at the MySQL Conference about
two weeks ago. The 1.0 GA offers virutally everything we needed for
Connector/ and MySQL Workbench.

Our own testing and the absence of bug reports on
makes me believe that the quality of the 1.0 is good. 1.0 seems to be a
good starting point. It does not have any super-fancy features. But it
certainly is a good basis for the future.

We follow the JDBC-API widely, we have Prepared Statements, we have
buffered and unbuffered result sets, we have an interface to fetch
BLOB/LOB data and all the basic SQL operations - including calling
stored functions - work fine. I know that we need to demo some of the
features, but they are available already. For 1.0.6 (before July) we
will check the performance and write some performance regression tests.

However, where shall we go from here: what do you want to see in 1.1,
1.5, 2.0 or 3.0? What do you need?

We have a first idea for 1.1, but I'd like to hear from you before we
make any suggestions.


Options: ReplyQuote

Written By
Which features do you want for 1.1, 1.5, 2.0?
May 06, 2009 02:13PM

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.