You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(3) |
Oct
(1) |
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(7) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(5) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2002 |
Jan
|
Feb
(1) |
Mar
|
Apr
(3) |
May
(3) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
(1) |
Oct
(15) |
Nov
(23) |
Dec
|
2003 |
Jan
|
Feb
(6) |
Mar
(5) |
Apr
(11) |
May
(8) |
Jun
|
Jul
|
Aug
(5) |
Sep
(4) |
Oct
(5) |
Nov
(7) |
Dec
(19) |
2004 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
(24) |
Sep
(2) |
Oct
(4) |
Nov
(3) |
Dec
(2) |
2005 |
Jan
(3) |
Feb
|
Mar
(6) |
Apr
|
May
(5) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
(2) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
(4) |
Feb
(5) |
Mar
|
Apr
(2) |
May
(3) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Andrew T. <ato...@aj...> - 2007-03-01 05:51:59
|
I would like to propose a group of changes. I have downloaded and made the following changes on my copy. Overloaded Constructor for Connection object: Connection(); Connection(const std::string& hostName); Connection(const std::string& hostName, const std::string& userName); Connection(const std::string& hostName, const std::string& userName, const std::string& pwd); Connection(const std::string& hostName, const std::string& userName, const std::string& pwd, unsigned int portNumber); Connection(const std::string& hostName, const std::string& userName, const std::string& pwd, const std::string& strDatabaseName); This way the a connection on the heap can be made by using the command mysqlcppapi::Connection *con = new mysqlcppapi::Connection( "localhost", "username", "password", "databasename"); This is less wordy then all the lines used to create a connection. Making connections and queries on the heap brings up another item. But before I go into that I need to give a reason for this. The reason to create these things as pointers on the heap is that they can be created and deleted by the program running them without creating memory leaks, while keeping the memory footprint to a minimum. The most important thing is to be able to hold the classes loosely coupled. This way a query can be made, drop the data into the result set and then be deleted. This leaves a small memory footprint. So the problem with this, is the function: Query Connection::create_Query() { return Query(*this); } It cannot be overloaded, so the next best thing is: Query *Connection::create_new_Query() { return new Query(*this); } Using the function above, a query on the heap can be using the command mysqlcppapi::Query *query = con->create_new_Query(); Another option is to remove it or go without it, using: mysqlcppapi::Query *query = new Query(con); I am going to be making a lot of changes and adding features to my copy of this API in order to get it to the point where I can use it in a GUI front end that I hope to be developing. These include adding Doxybook documentation; transactions; database, table and field discovery classes, while keeping the classes as simple as possible and loosely coupled in order to keep them easy to use. I need to know how to communicate those changes back, as proposals, to the person maintaining the project. |
From: Jonathan W. <my...@ka...> - 2007-01-19 01:23:40
|
The mysqlcppapi-main mailing list is now almost dead - it gets one real post every six months and several spam posts per day, so I plan to close this list. If you still use mysqlcppai, either mail me back to ask for this project to continue, or switch to mysql++ at http://tangentsoft.net/mysql++/ Please, if you use this project say so in the next 2-3 monnths or it will be wound up in favour of mysql++ (which is not run by an idiot nowadays) jon |
From: Louis <hl...@gm...> - 2007-01-09 15:21:13
|
I'm compiling the mysqlcppapi rc 2.0 under windows vs 2005 there are always a error in allocator.h, here is the log: 1> e:\project\samples\mysqlcppapi-2.0.0\mysqlcppapi\smartpointer\allocator.h(35 ) : error C2512: 'mysqlcppapi::Connection' : no appropriate default constructor available 1> e:\project\samples\mysqlcppapi-2.0.0\mysqlcppapi\smartpointer\allocator.h(34 ) : while compiling class template member function 'mysqlcppapi::Connection *mysqlcppapi::Allocator_NewDelete<T_cobj>::allocate(void)' 1> with 1> [ 1> T_cobj=mysqlcppapi::Connection 1> ] 1> e:\project\samples\mysqlcppapi-2.0.0\mysqlcppapi\smartpointer\sharedptr.h(22 3) : see reference to class template instantiation 'mysqlcppapi::Allocator_NewDelete<T_cobj>' being compiled 1> with 1> [ 1> T_cobj=mysqlcppapi::Connection 1> ] 1> e:\project\samples\mysqlcppapi-2.0.0\mysqlcppapi\smartpointer\sharedptr.h(20 7) : while compiling class template member function 'void mysqlcppapi::SharedPtr<T_obj>::unref(void)' 1> with 1> [ 1> T_obj=mysqlcppapi::Connection 1> ] 1> e:\project\samples\mysqlcppapi-2.0.0\mysqlcppapi\smartpointer\sharedptr.h(13 0) : while compiling class template member function 'mysqlcppapi::SharedPtr<T_obj>::~SharedPtr(void)' 1> with 1> [ 1> T_obj=mysqlcppapi::Connection 1> ] 1> e:\project\samples\mysqlcppapi-2.0.0\mysqlcppapi\query_results\result_use.h( 54) : see reference to class template instantiation 'mysqlcppapi::SharedPtr<T_obj>' being compiled 1> with 1> [ 1> T_obj=mysqlcppapi::Connection 1> ] I haven't change any code the Connection, allocator.h, and SharedPtr any tips was appreciated :) |
From: Igor V. C. <igo...@ya...> - 2006-05-09 01:22:41
|
Hi all, First at all, I must congratulations all people that help and built this very useful library. But, I felt bad because the project doesn't have a good documentation. Something like "Javadoc" that helps a lot to understand and use the library. I know that the good examples programs came to help, but isn't enought! Are you planning to document the code? Maybe, something like Doxygen (http://www.stack.nl/~dimitri/doxygen/) can help ... I'm doing the documentation in Brazilian Portuguese using Doxygen, but I'll feel happy if you incorporate this "plus" in your new source code... Is it possible? That's it, congratulations and keep going ... -- ---- ------- -------- ~ Igor Vitório Custódio (igorvc) ' v ' PLACA - ENC 03 - UFSCar / / \ \ E-Mail: igo...@ya... / ( ) \ http://www.igor.uni.cc ^ ` ~ ' ^ Linux User: #322156 |
From: Jim L. <jim...@gm...> - 2005-12-27 13:23:06
|
I'm running on a debian sarge system and the links to /usr/share/automake- 1.9 don't exist. I have the packages autotools-dev and pkg-config install but neither of them include an automake. I even did a find / -print | grep -i automake. No go. Somehow I don't think this package is very universal. Thanks for any pointers. Jim. |
From: Jonathan W. <re...@us...> - 2005-08-31 23:02:48
|
NHAN VAN HOANG wrote: > Hi, > > My name is Tony Hoang, a student from CSUSM. I have a problem with installing mysqlcppapi-1.9.3. I can run ./configure and make, but can not run make install as it gives me the following messages: > > make[1]: Entering directory `/home/hoang006/mysqlcppapi-1.9.3/e > make[1]: Nothing to be done for `install-exec-am'. > make[1]: Nothing to be done for `install-data-am'. > make[1]: Leaving directory `/home/hoang006/mysqlcppapi-1.9.3/ex > > All so the connection object had not been created. > /usr/include/mysql/mysql.h: In member function `bool > mysqlcppapi::Connection::shutdown()': > /usr/include/mysql/mysql.h:470: too few arguments to function > mysql_shutdown(MYSQL*, mysql_enum_shutdown_level)' > Connection.cc:215: at this point in file Hi Tony, the number of arguments to mysql_shutdown() changed, so you need a change to mysqlcppapi which has not been released yet. If you use the latest version from CVS (available from the http://sourceforge.net/projects/mysqlcppapi page) it should work OK. Sorry there hasn't been a new release yet. jon -- "I was born not knowing and have had only a little time to change that here and there." - Feynman |
From: NHAN V. H. <hoa...@sb...> - 2005-08-31 05:56:45
|
Hi, My name is Tony Hoang, a student from CSUSM. I have a problem with installing mysqlcppapi-1.9.3. I can run ./configure and make, but can not run make install as it gives me the following messages: make[1]: Entering directory `/home/hoang006/mysqlcppapi-1.9.3/e make[1]: Nothing to be done for `install-exec-am'. make[1]: Nothing to be done for `install-data-am'. make[1]: Leaving directory `/home/hoang006/mysqlcppapi-1.9.3/ex All so the connection object had not been created. /usr/include/mysql/mysql.h: In member function `bool mysqlcppapi::Connection::shutdown()': /usr/include/mysql/mysql.h:470: too few arguments to function mysql_shutdown(MYSQL*, mysql_enum_shutdown_level)' Connection.cc:215: at this point in file Thank you, Tony Hoang |
From: Pat D. <cod...@ps...> - 2005-07-22 00:45:52
|
Greets, Not sure which version you are using but my install has no such constructor... only: // default c'tor Connection(); ///The copy will share the underlying connection. Connection(const Connection& src); are available in Connection.h. Other than that, there are a bunch of little issues in your example (e.g. "const char dbV" is a constant *single* character where you're actually looking for a pointer). Anyhow, here's how I've been doing it normally: =============================== snip ============================= #include <mysqlcppapi/Connection.h> #include <string> int main() { mysqlcppapi::Connection con; const std::string dbV("test"), hostV("localhost"), userV("root"), passwdV("somepassword"); // set up auth con.set_Host(hostV); con.set_User(userV); con.set_Password(passwdV); // actually connect con.connect(); if (! con.is_connected()) { // do something about it... return 1; } // select the db con.select_database(dbV); // check if it worked, do stuff... return 0; } =============================== snip ============================= HTH and regards, -- Pat Deegan http://www.psychogenic.com |
From: Greg T. <gtaylor@CLEMSON.EDU> - 2005-07-21 21:07:57
|
I'm still very new to C++ so I'm probably doing this all wrong, but I was=20 modifying the example program to specify a host/user/db and this is what I= =20 did: int main() { // The full format for the Connection constructor is // Connection(cchar *db, cchar *host=3D"", // cchar *user=3D"", cchar *passwd=3D"") // You may need to specify some of them if the database is not on // the local machine or your database username is not the same as your // login name, etc.. try { const char dbV =3D "test"; const char hostV =3D "localhost"; const char userV =3D "root"; const char passwdV =3D "somepassword"; mysqlcppapi::Connection(&dbV, &hostV, &userV, &passwdV) con; I get the following error on compile: gtaylor@devbox1:~/mysql/example/src$ make g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2=20 =2DI/usr/local/include/mysqlcppapi-2.0 -I/usr/local/lib/mysqlcppapi-2.0/inc= lude=20 =2DI/usr/mysql/include -c simple1.cc simple1.cc: In function `int main()': simple1.cc:17: error: invalid conversion from `const char*' to `char' simple1.cc:18: error: invalid conversion from `const char*' to `char' simple1.cc:19: error: invalid conversion from `const char*' to `char' simple1.cc:20: error: invalid conversion from `const char*' to `char' simple1.cc:22: error: no matching function for call to=20 `mysqlcppapi::Connection ::Connection(const char*, const char*, const char*, const char*)' /usr/local/include/mysqlcppapi-2.0/mysqlcppapi/Connection.h:32: error:=20 candidates are: mysqlcppapi::Connection::Connection(const mysqlcppapi::Connection&) /usr/local/include/mysqlcppapi-2.0/mysqlcppapi/Connection.h:29: error: mysqlcppapi::Connection::Connection() simple1.cc:22: error: parse error before `;' token simple1.cc:26: error: `con' undeclared (first use this function) simple1.cc:26: error: (Each undeclared identifier is reported only once for each function it appears in.) make: *** [simple1.o] Error 1 Any ideas? |
From: Jonathan W. <co...@co...> - 2005-05-24 14:09:18
|
On Mon, May 23, 2005 at 09:31:05PM +0100, Jonathan Wakely wrote: > I would prefer to use is_null() for both getting and setting the value: > > version 1.7 version 1.9 version 2.0 > GET: bool is_null() const -> bool ism_bNull() -> bool is_null() Oops, there are "const" qualifiers missing there ... obviously I don't plan to make the functions non-const. jon -- "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." - Doug Gwyn |
From: Jonathan W. <co...@co...> - 2005-05-23 20:31:57
|
On Tue, May 17, 2005 at 12:24:14PM -0700, Julian Pellico wrote: > Hi, Hi Julian, > How can I determine whether a ColData item is null across versions of > this library? I'm afraid a macro might be the only way. > The test in the old version I was using was is_null(), but in a newer > version it's ism_bNull(). I would prefer to write code that can be > linked against either of these versions... (Are you using the released packages on sourceforge.net or CVS?) I'm not a big fan of the naming convention used in ColData, although I don't like the old names either. For the record: version 1.7 version 1.9 GET: bool is_null() const -> bool ism_bNull() const SET: void it_is_null() -> void is_null() I don't like ism_bNull() at all, since it uses the name of a private variable in the public interface. This exposes implementation detail and makes the name of the function hard to remember unless you know the implementation. I would prefer to use is_null() for both getting and setting the value: version 1.7 version 1.9 version 2.0 GET: bool is_null() const -> bool ism_bNull() -> bool is_null() SET: void it_is_null() -> void is_null() -> void is_null(bool) is_null() with no argument queries the value and is_null() with argument modifies it. Unfortunately, I don't think it will be possible to switch between a new version and 1.7 and be link-compatible. jon |
From: Julian P. <jpe...@ha...> - 2005-05-17 19:24:34
|
Hi, How can I determine whether a ColData item is null across versions of this library? The test in the old version I was using was is_null(), but in a newer version it's ism_bNull(). I would prefer to write code that can be linked against either of these versions... Thanks, Julian |
From: Jonathan W. <co...@co...> - 2005-03-10 15:51:08
|
On Thu, Mar 10, 2005 at 11:55:07AM +0100, Radoslaw Garbacz wrote: > On Thursday 10 March 2005 11:10, Jonathan Wakely wrote: > > That change is also in CVS already. I'll try to make a release this > > weekend. > > I see that everything has already been done :-) > - sorry for not checking the CVS. No, it's my fault for not releasing the improvements properly. > > Another, simpler alternative would be to allow you to check an error code. > > That would mean you don't need to match strings but we don't have to define > > a whole hierarchy of classes. I'll have a think about it when I get a > > chance at the weekend. > > Yes, this is the best solution, and it would be enough for me. OK, I'll do something along these lines. jon |
From: Radoslaw G. <rga...@ay...> - 2005-03-10 10:55:31
|
On Thursday 10 March 2005 11:10, Jonathan Wakely wrote: > That change is also in CVS already. I'll try to make a release this > weekend. I see that everything has already been done :-) - sorry for not checking the CVS. > Another, simpler alternative would be to allow you to check an error code. > That would mean you don't need to match strings but we don't have to defi= ne > a whole hierarchy of classes. I'll have a think about it when I get a > chance at the weekend. Yes, this is the best solution, and it would be enough for me. Thank you for your help. =2D-=20 Mit freundlichen Gr=FC=DFen Best regards =20 // Radoslaw Garbacz // aycan Digitalsysteme GmbH // Innere Aumuehlstrasse 5 // 97076 Wuerzburg // Germany // phone: +49 931.270 40 90 // fax: +49 931.270 40 91 // mailto:rga...@ay... // http://www.aycan.de |
From: Jonathan W. <co...@co...> - 2005-03-10 10:11:20
|
On Thu, Mar 10, 2005 at 10:34:48AM +0100, Radoslaw Garbacz wrote: > Hi, > > Thank you for the quick response. Hi Radoslaw, > On Tuesday 08 March 2005 14:19, you wrote: > > Yes, or sending it to this list might get a quicker response. > > Considering the fact that "mysql_shutdown" is already done there is almost > nothing to change, just the file: mysqlcppapi/ColData.h > @@ -221,7 +221,7 @@ > > > template <class T_Str> template<class Type> > -Type ColData_Generic<T_Str>::conv(Type dummy) const > +Type ColData_Generic<T_Str>::conv(Type /*dummy*/) const > { > std::string strbuf(buf); > strip_all_blanks(strbuf); That change is also in CVS already. I'll try to make a release this weekend. > > > I would like to ask, if it was possible, for the more complex exceptions > > > scheme - for now I have to check the exception's description to check the > > > reason (e.g. all "artificial deadlocks" of MySQL which, as they suggest, > > > should cause transactions retrial). > > > > That's a good idea, feel free to post suggestions to this list. > > The failure reasons I have to check by comparing strings: > 1. mysqlcppapi::ex_BadQuery.what() == "Duplicate entry" > the_proposal: ex_DuplicateEntry > > 2. mysqlcppapi::ex_BadQuery.what() == "mysql_real_connect() failed" > the_proposal:ex_ConnectionFailure > > 3. mysqlcppapi::ex_BadQuery.what() == ".*try restarting transaction.*" > The suggestion to restart the transaction can happen in various situations, > so I check the existence of this phrase inside the exception description. > the_proposal: ex_InternalTimeout | ex_TransRestart > e.g. ex_InternalDeadLock: public ex_InternalTimeout Another, simpler alternative would be to allow you to check an error code. That would mean you don't need to match strings but we don't have to define a whole hierarchy of classes. I'll have a think about it when I get a chance at the weekend. > I also added files such as: AUTHOR, COPYING, etc. to the set of files being btw I plan to rename COPYING to COPYING.LIB since the file is a copy of the LGPL. > installed - it is prepared for SuSE like directories scheme (packages' > documentation is placed in "/usr/share/doc/packages/<package>") - to make it > in a traditional way ("/usr/share/package") just the line: > pkgdatadir = $(datadir)/doc/packages/@PACKAGE@ > has to be removed from the main Makefile.am OK, I might ask you more about this when I prepare a release. > I have the SPEC to build RPMs so if you were interested you can use it > (please check whether there is no LGPL license violation). Thanks, there are a couple of things I'd change. The library is LGPL licensed, but the spec file says GPL. I would also change the description to make it clear mysqlcppapi is an incompatible fork, not just a modified version of mysql++. Thanks again for your suggestions, I'll be in touch again soon jon -- "Fanaticism consists in redoubling your efforts when you have forgotten your aims." - George Santayana |
From: Radoslaw G. <rga...@ay...> - 2005-03-10 09:35:07
|
Hi, Thank you for the quick response. On Tuesday 08 March 2005 14:19, you wrote: > Yes, or sending it to this list might get a quicker response. Considering the fact that "mysql_shutdown" is already done there is almost= =20 nothing to change, just the file: mysqlcppapi/ColData.h @@ -221,7 +221,7 @@ =20 =20 template <class T_Str> template<class Type>=20 =2DType ColData_Generic<T_Str>::conv(Type dummy) const +Type ColData_Generic<T_Str>::conv(Type /*dummy*/) const { std::string strbuf(buf); strip_all_blanks(strbuf); > > I would like to ask, if it was possible, for the more complex exceptio= ns > > scheme - for now I have to check the exception's description to check t= he > > reason (e.g. all "artificial deadlocks" of MySQL which, as they suggest, > > should cause transactions retrial). > > That's a good idea, feel free to post suggestions to this list. The failure reasons I have to check by comparing strings: 1. mysqlcppapi::ex_BadQuery.what() =3D=3D "Duplicate entry" the_proposal: ex_DuplicateEntry 2. mysqlcppapi::ex_BadQuery.what() =3D=3D "mysql_real_connect() failed" the_proposal:ex_ConnectionFailure 3. mysqlcppapi::ex_BadQuery.what() =3D=3D ".*try restarting transaction.*" The suggestion to restart the transaction can happen in various situations= , =20 so I check the existence of this phrase inside the exception description. the_proposal: ex_InternalTimeout | ex_TransRestart e.g. ex_InternalDeadLock: public ex_InternalTimeout I also added files such as: AUTHOR, COPYING, etc. to the set of files bein= g=20 installed - it is prepared for SuSE like directories scheme (packages'=20 documentation is placed in "/usr/share/doc/packages/<package>") - to make i= t=20 in a traditional way ("/usr/share/package") just the line: pkgdatadir =3D $(datadir)/doc/packages/@PACKAGE@ has to be removed from the main Makefile.am I have the SPEC to build RPMs so if you were interested you can use it=20 (please check whether there is no LGPL license violation). Attached:=20 =2D the patch against the version 1.9.3 =2D the spec file =2D-=20 Mit freundlichen Gr=FC=DFen Best regards =20 // Radoslaw Garbacz // aycan Digitalsysteme GmbH // Innere Aumuehlstrasse 5 // 97076 Wuerzburg // Germany // phone: +49 931.270 40 90 // fax: +49 931.270 40 91 // mailto:rga...@ay... // http://www.aycan.de |
From: Jonathan W. <co...@co...> - 2005-03-08 13:20:29
|
On Tue, Mar 08, 2005 at 01:48:04PM +0100, Radoslaw Garbacz wrote: > Hello, Hi, > I am the newbe with using the sourceforge so sorry for my lack of knowledge. > > I have been using the mysqlcppapi library successfully for some time, so at > first I would like to thank all maintainers and developers for the good work > they have done. Thanks for the kind words (I am the current maintainer but can't take credit for much of the library myself). > I did some slight changes to the package and I would like to ask where shell > I send the patch? Is the sourceforge project's <patches> link the right place > to do it? Yes, or sending it to this list might get a quicker response. > The changes are quite minor - I just got rid of few warnings during the > compilation (defined but not used methods' parameters) and corrected > "mysql_shutdown" invocation to match the new MySQL interface (4.1.10) - but > without preprocessor directives to check the MySQL version (sorry). Please check the latest version from CVS, at least the mysql_shutdown change is already done. I *badly* need to make a new release incorporating those changes. > I would like to ask, if it was possible, for the more complex exceptions > scheme - for now I have to check the exception's description to check the > reason (e.g. all "artificial deadlocks" of MySQL which, as they suggest, > should cause transactions retrial). That's a good idea, feel free to post suggestions to this list. jon -- "You will find that the state is the kind of organization which, though it does big things badly, does small things badly too." - John Kenneth Galbraith |
From: Radoslaw G. <rga...@ay...> - 2005-03-08 12:48:23
|
Hello, I am the newbe with using the sourceforge so sorry for my lack of knowledg= e. I have been using the mysqlcppapi library successfully for some time, so a= t=20 first I would like to thank all maintainers and developers for the good wor= k=20 they have done. I did some slight changes to the package and I would like to ask where she= ll=20 I send the patch? Is the sourceforge project's <patches> link the right pla= ce=20 to do it? The changes are quite minor - I just got rid of few warnings during the=20 compilation (defined but not used methods' parameters) and corrected=20 "mysql_shutdown" invocation to match the new MySQL interface (4.1.10) - but= =20 without preprocessor directives to check the MySQL version (sorry).=20 =20 I would like to ask, if it was possible, for the more complex exceptions=20 scheme - for now I have to check the exception's description to check the=20 reason (e.g. all "artificial deadlocks" of MySQL which, as they suggest,=20 should cause transactions retrial). Thanks in advance for any suggestions and help about my question and the=20 changes I made as well. =2D-=20 Mit freundlichen Gr=FC=DFen Best regards =20 // Radoslaw Garbacz // aycan Digitalsysteme GmbH // Innere Aumuehlstrasse 5 // 97076 Wuerzburg // Germany // phone: +49 931.270 40 90 // fax: +49 931.270 40 91 // mailto:rga...@ay... // http://www.aycan.de |
From: Jonathan W. <co...@co...> - 2005-01-21 15:00:17
|
On Fri, Jan 21, 2005 at 03:38:48PM +0100, Patrick Ruckstuhl wrote: > Hi, Hi, > has anyone used (or tried to use) mysqlcppapi 1.9.3 with an amd64 > architecture? > > Were there any problems? My box at home is x86_64, and mysqlcppapi compiles fine. Can't remember any problems, but I didn't test exhaustively. If you find any problems I can easily test and fix them, since I have an x86_64 box. jon -- "It's no good pretending that any relationship has a future if your record collections disagree violently, or if your favorite films wouldn't even speak to each other if they met at a party." - Nick Hornby |
From: Patrick R. <ru...@so...> - 2005-01-21 14:39:17
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, has anyone used (or tried to use) mysqlcppapi 1.9.3 with an amd64 architecture? Were there any problems? Regards, Patrick Ruckstuhl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB8RP43y5tALuHRTgRAhCzAJ9bbh0Z0Vjx8TeBcpF5plSz2fPQQQCfcnyo S0eAbVypTzjG3PfGFKudumE= =EYvD -----END PGP SIGNATURE----- |
From: Jonathan W. <co...@co...> - 2005-01-07 13:58:08
|
On Sat, Dec 25, 2004 at 05:18:41AM +0100, Christoffer Brodd-Reijer wrote: > A time ago I had several problems getting MySQL++ to work. It was too > difficult and not very easy to install and use. Then I saw this, I had a > lot of problem here too but then it worked. > > Now I updated mysql to 5.0.2 and now mysqlcppapi is spitting out all > kind of errors. This problem has actually been fixed already for 5 months. I need to make a new release, but in the meantime you can get the latest code from CVS on the sourceforge project page. jon -- "Sell your cleverness and buy bewilderment: Cleverness is mere opinion, bewilderment is intuition." - Jalal-uddin Rumi |
From: Jonathan W. <co...@co...> - 2004-12-27 19:18:52
|
First of all, sorry for the delay in approving this mail for delivery, but I've been away for Christmas. On Sat, Dec 25, 2004 at 05:18:41AM +0100, Christoffer Brodd-Reijer wrote: > A time ago I had several problems getting MySQL++ to work. It was too > difficult and not very easy to install and use. Then I saw this, I had a > lot of problem here too but then it worked. If you report problems on this list I'll do what I can to help. > Now I updated mysql to 5.0.2 and now mysqlcppapi is spitting out all > kind of errors. > > Is mysqlcppapi serious or just a hobby? There is no documentation on the > usage of it. I had to look at a few examples and examine the header-files. As the website says, it was forked from MySQL++ to provide an alternative that is a bit less broken. It's neither a work of love nor a mission-critical piece of infrastructure for anyone so it only gets maintained as people report bugs or when I find time to slowly improve it. It's not just a hobby, but I no longer use it for any code, either personal or professional. More documentation would obviously be nice, but I'm afraid I don't have time to add it myself at the moment. > And are you about to update the code so it will work with mysql 5.0.2 soon? Yes, as you've reported this I'll download the 5.0 sources and make sure mysqlcppapi works with it. I've had bad experiences with new releases from MySQL A.B and as I mainly develop with mysql on important projects at work I only use stable versions, so hadn't noticed this problem. > Here are the errors I got when compiling: > > /usr/local/mysql/include/mysql/mysql.h: In member function `bool > mysqlcppapi::Connection::shutdown()': > /usr/local/mysql/include/mysql/mysql.h:458: error: too few arguments to > function `int mysql_shutdown(MYSQL*, mysql_enum_shutdown_level)' > Connection.cc:215: error: at this point in file This shouldn't be hard to fix - IIRC they changed the signature of that function in the 4.x API as well, so there's already a #if around that function to test the MySQL version. Thanks for reporting the problem, I'll let you know when I've fixed it. It probably won't be until the New Year, as I'm about to go on holiday again for a few days. Season's Greetings to everyone reading this, jon -- -- "He who joyfully marches to music in rank and file has already earned my contempt. He has been given a large brain by mistake, since for him the spinal cord would fully suffice." - Albert Einstein |
From: Christoffer Brodd-R. <chr...@mb...> - 2004-12-25 04:18:51
|
A time ago I had several problems getting MySQL++ to work. It was too difficult and not very easy to install and use. Then I saw this, I had a lot of problem here too but then it worked. Now I updated mysql to 5.0.2 and now mysqlcppapi is spitting out all kind of errors. Is mysqlcppapi serious or just a hobby? There is no documentation on the usage of it. I had to look at a few examples and examine the header-files. And are you about to update the code so it will work with mysql 5.0.2 soon? Christoffer Here are the errors I got when compiling: /usr/local/mysql/include/mysql/mysql.h: In member function `bool mysqlcppapi::Connection::shutdown()': /usr/local/mysql/include/mysql/mysql.h:458: error: too few arguments to function `int mysql_shutdown(MYSQL*, mysql_enum_shutdown_level)' Connection.cc:215: error: at this point in file |
From: Jonathan W. <co...@co...> - 2004-11-25 13:20:40
|
Hi Andrew there are no reference docs for mysqlcppapi unfortunately. You could look at the example files included in the distribution, or you can also look at the docs for MySQL++ (if you can find them online) but be aware that mysqlcppapi has changed and is not the same as MySQL++ now. jon -- "Consistency is the last refuge of the unimaginative." - Oscar Wilde |
From: Andrew M. <am...@de...> - 2004-11-24 13:11:19
|
Hello, Could I please be directed to a resource, online preferrably, or a book, that would let me know how to use the mysqlcppapi wrapper? Thank you. Andrew M. |