SCO/RCO: cannot retrieve object

[Kato]

Hi there,

I'm having some problems retrieving stored objects from a MySQL table with RCO. SCO seems to store the object in the table though, I can see it while browsing the table with MySQL Query Browser. I'm using a simplified system wich stores/retrieves a npc, looping through it's inventory to retrieve items. I thought about trying FETCHMODE, but I'm under Windows, alas...

The functions:

void SetPersistentObject(string sKey, object oObject)
{
string sSQL = "INSERT INTO bankobj(cdkey, storer) VALUES('" + sKey + "', %s) ON DUPLICATE KEY UPDATE storer=%s";
SetLocalString(GetModule(), "NWNX!ODBC!SETSCORCOSQL", sSQL);
StoreCampaignObject("NWNX", "-", oObject);
}

object GetPersistentObject(object oPC, object oOwner)
{
string sKey = GetPCPublicCDKey(oPC);
string sSQL = "SELECT storer FROM bankobj WHERE cdkey='" + sKey + "'";
SetLocalString(GetModule(), "NWNX!ODBC!SETSCORCOSQL", sSQL);
if(!GetIsObjectValid(oOwner)) oOwner = oPC;
return RetrieveCampaignObject("NWNX", "-", GetLocation(oOwner), oOwner);
}

my odbc log file:

o Got request (scorco): SELECT storer FROM bankobj WHERE cdkey='Q7KUVYJJ'
o Got request (scorco): INSERT INTO bankobj(cdkey, storer) VALUES('Q7KUVYJJ', ~s) ON DUPLICATE KEY UPDATE storer=~s
! SQL Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '˜«ZàÒi' at line 1
o Got request (scorco): SELECT storer FROM bankobj WHERE cdkey='Q7KUVYJJ'
o Got request (scorco): INSERT INTO bankobj(cdkey, storer) VALUES('Q7KUVYJJ', ~s) ON DUPLICATE KEY UPDATE storer=~s
! SQL Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '˜«ZàÒi' at line 1

I feel like this must be very simple, sorry if it is, and thank you very much for taking the time to read this!

Kato

[Kato]

well, I guess I'll have to find out... I'll report my results when I do.

Kato

[Kato]

Okay, FYI, it simply was the ON DUPLICATE KEY UPDATE part wich caused the problem. Many thanks to Virusman for the info.