This is still beating me. I can confirm that simple queries execute and return a result
set fine (using the MySQL++ API). For example:
query << "SELECT NOW()";
mysqlpp::StoreQueryResult res = query.store();
cout << res[0][0] << endl;
query << "SELECT 42";
res = query.store();
cout << res[0][0] << endl;
query << "SELECT host__guid from host LIMIT 1";
res = query.store();
cout << res[0][0] << endl;
These all return 1 row with non-NULL data as expected. The SSQL stuff still won't work. I
have now tried vector, list and set all with this SSQL:
sql_create_2 (hdb_host_t, 1, 0,
sql_bigint_unsigned, id,
sql_int_unsigned, guid)
And each returns the correct no. of rows but all values are NULL (which they aren't!). I
have tried removing all MySQL packages from my machine, re-installing, ensuring only one
version of the library exists then rebuilding MySQL++ and all to no avail. So, you could
consider my system 'clean'.
Has something else changed that would affect my declaration above? The one that used to
work in 2.3.2!?
Regards,
Jim
----- Original Message -----
From: "Warren Young" <mysqlpp@stripped>
To: "MySQL++ Mailing List" <plusplus@stripped>
Sent: Thursday, 11 September, 2008 4:38:23 PM GMT +00:00 GMT Britain, Ireland, Portugal
Subject: Re: Result set count correct but each attribute is empty!
James Vanns wrote:
>
> I have to include <mysql/errmsg.h> still else these aren't found:
>
> mysql++-test.cpp:95: error: ‘CR_SERVER_LOST’ was not declared in this
> scope
Yes fine, just so long as you do it after mysql++.h.
> Yup. I did and now do again - still nothing is thrown :|
I don't actually you to catch new exceptions. If there were uncaught
exceptions, you'd be complaining of your program core dumping. I was
just layin' some generally good advice on you.
>> Have you tried it on a different machine?
>
> No.
Do. :)
If you can do it on a different OS, so much the better. You don't have
to go to the extreme of porting to Windows. Even something as minor as
moving from, say, RHEL3 to RHEL5 might provide enlightenment. Better
would be RHEL3 to Ubuntu 8.04.1. Even better would be RHEL3 to Open
Solaris 10.
I say this because I think there must be some local difference there.
You can't reproduce the problem in the sandbox we can both play in, so
you'll have to make a new sandbox for yourself to try and flush out that
local difference.
I guess another thing to try would be the svn version of MySQL++. My
tests here have been against that, not the 3.0.6 release version.
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsub=1
--
James Vanns
Systems Programmer
Framestore CFC Ltd.
