23 messages in com.mysql.lists.plusplusRe: Connection::connect() interface i...
FromSent OnAttachments
Warren Young12 Jul 2007 20:20 
Drew M.12 Jul 2007 21:32 
Yuan...@csiro.au12 Jul 2007 22:28 
Warren Young12 Jul 2007 22:44 
Warren Young12 Jul 2007 22:50 
Joel Fielder13 Jul 2007 00:41 
Axel Howind13 Jul 2007 01:17 
Alex Burton13 Jul 2007 01:20 
Jim Wallace13 Jul 2007 04:07 
William F. Dowling13 Jul 2007 06:23 
Warren Young13 Jul 2007 21:19 
Warren Young13 Jul 2007 21:26 
Warren Young13 Jul 2007 21:30 
Warren Young13 Jul 2007 21:42 
Warren Young13 Jul 2007 21:49 
Alex Burton15 Jul 2007 06:38 
Peter Garner15 Jul 2007 09:36 
Joel Fielder16 Jul 2007 01:56 
Axel Howind16 Jul 2007 03:34 
Warren Young16 Jul 2007 04:59 
Warren Young16 Jul 2007 05:07 
Axel Howind16 Jul 2007 07:06 
Warren Young16 Jul 2007 07:19 
Subject:Re: Connection::connect() interface is changing
From:Warren Young (mysq@etr-usa.com)
Date:07/12/2007 10:50:46 PM
List:com.mysql.lists.plusplus

Yuan@csiro.au wrote:

It would be good to keep the old Connection when you add new one.

Unfortunately, I can't think of a way to make that happen. So many of the parameters are default that any overload I can think of is ambiguous. If you can come up with one, do propose it.

The only thing that's really on the table is whether the server_addr and password parameters should be swapped back. For most uses of the library, that would make the new interface compatible with the old one. The only people who will see a difference are those who were passing values for the port, compress, connect_timeout, socket_name, and client_flag parameters. I think I've adequately justified removing all of these.

Maybe using std::string instead of cchar* makes the code more C++ way.

const char* converts to std::string directly. It'd still be ambiguous.

By the way, thank you for your hard work on SSQLS and BLOB. I tested v2.3.2 and they are working perfectly.

Thanks for letting me know!