SQLFetch Problems (I Think!)

[scarface]

Hello, I am trying to modify some APS functions to work with my banking system, but from what I can tell, whenever I use SQLFetch() it always returns SQL_ERROR regardless of whether the row exists or not, here are a couple of the modified functions:

[Disco]

Take a look at your SQL log and post the SQL query that fails?

[scarface]

Hmmm, it seems to work now, but I have another issue, I have an xp bank also, the table should be the same to store xp and gold, example:

Empty Table 'banking':

[scarface]

Ok the problem is solved, Funkyswerve helped me with it, he didn't have time for a request though, I wanted to add item banking to the table too. With my banking system, a creature holds all of the player's items, and then the creature is stored to the database, I would like to know how object's can be stored into this table like so:

[Disco]

You realise that this way of storing is an open invitation to muling items, right?

[scarface]

[Disco]

There's a function for it in aps_include. Check that and take out all stuff you don't need.

[scarface]

[Gryphyn]

[scarface]

[Disco]

Make sure you strip any quotes from the varname with SQLEncodeEtc().

I alse use the Blob data type in the table, but I guess Text will work as well. The function is meant to store an object in the BioWare db and I bet that's been done as a string.

The method you follow gives a big overhead. Try this:

Table:

id (type=int, length=11, primary key, auto increment)
cdkey (type=string, length=8, index key)
item_name (type=string, length=128, index key)
item_data (type=blob, length=65535 )

You store items you put in a box following the previous post.

Now, you retrieve a list of what's in store by

"SELECT id, item_name FROM MyObjects WHERE cdkey='XYZ12345' "

Loop that into a convo and retrieve individual items with

"SELECT item_data FROM MyObjects WHERE id=134"

That way you don't have to store a whole NPC every time.

[scarface]

[Disco]

Depends on what you call efficient. If you want to minimise calls whole object storing is indeed better, but you need to move the whole block of data just to look at what's in it, so it isn't efficient if you look at the amount of data transfered between SQL and NWN. With a bit of effort you can get PC objects of about 1 MB, and moving that repeatedly isn't a trivial load.

[scarface]

[FunkySwerve]

When using NWNX-MySQL, the difference in performance is negligible, since the biggest hit is the ingame object creation - do enough and it'll down your server. This is NOT ameliorated by spawning in the creature, since all its items are also spawned in and added as objects. This is why you see additional spawn lag on creatures wearing lots of gear, incidentally. In any event, because MySQL calls are blazing fast compared to Campaign ints, there's absolutely no reason to do it this way, and every reason not to, since as a previous poster pointed out, it prevents you from viewing or manipulating the items individually, one of the prime advantages of MySQL to begin with. Basically, the way you're doing makes perfect sense when using the Bioware database, and none at all when using MySQL. Which is of course why I suggested you use the provided functions, to begin with. You are reinventing a square wheel.

Funky