Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
Subject: mysql openssl Question
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
Update one field with more fields from another table
Subject: Getting Identity after INSERT
ERROR 2002: Can 't connect to local MySQL server through socket
mysql test 4 1 fails with the gis test
Subject: MySQL Cluster Software
Downgrade Mysql from 4 to 3 23
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Can 't access mysql after kernel upgrade
Executing MySQL Commands From Within C Program
Comparing and writing out BLOBS
Subject: Re: Preventing Duplicate Entries
FULLTEXT query format question
Strange behavior, Table Level Permission
Does the binary log enabling affect the MySQL performances?
mysql:it 's a db not a dbms how it 's possible?!
mysql have same function mthod as Oracle decode()
 
v2.3.2 and execute?

v2.3.2 and execute?

2007-10-04       - By Jim Wallace

 Back
Please point me to the link if this has already been answered.  I tried
search the archive, but I didn't find a good hit.

I recently got a point in my project to update from 2.1.1 to 2.3.2.  The
migration went smoothly, with one post 2.3.2 fix I found I needed.  Now
I found this one, but don't know if it has been fixed.

In 2.1.1 this worked fine, and execute() would use the two parameters as
query parameters just fine.

clan_name is const char *
player->m_handle is int

query << "INSERT INTO clans ( clan_name, owner_id ) VALUES (%0q, %1)";
query.parse();
ResNSel res = query.execute( clanName, player->m_handle );

But in 2.3.2, it now uses a this method (execute (const char *str,
size_t len)) that thinks clanName is the SQL statement, and
player->m_handle is the length, so, of course, if fails.

To get around it I switched the parameter around, but was curious if
there was a fix to avoid the confusion?

Thanks,
jmw

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe:    http://lists.mysql.com/plusplus?unsub=mysql@(protected)