Method of Automatic Table Creation?

[Spawnblade]

As the subject indicates. Just taught myself the basics of nwnx2 and sqlite a few days back in order to move away from using Bioware's generally slower database.

Now perhaps I'm spoiled, but NWN's default database was easily organized via creating new campaign databases that could be simply wiped if desired. I had thought on first look that the table column would accommodate this nicely using ODBC2.. However I quickly learned that sqlite will not automatically create tables that are being referenced.

So is there any code I could possibly add to the ODBC2 functions to allow this dynamic table creation when a table of that name doesn't exist?

If not, is the best method to simply rewrite every function to accommodate an extra 'identifier' variable for organizational purposes?

And last, what program do you guys recommend for viewing/editing the actual database (any third party programs that work graphically rather than constantly utilizing command lines?) And will any of them sort based on column information to allow better viewing? (I've determined SQLiteCC to be inadequate for me )

I appreciate any help that can be given . I'll go back to searching the topics to ensure I didn't miss any relevant info.

[FunkySwerve]

You could do that, yes, but you would probably be better served by figuring out what data you're storing, what tables you want to store it in, and how they'll relate to each other, if at all, intead of just trying to automate table creation. When I first transferred over, I simply copied all my bioware vars into the default table that comes with nwnx, merging the campaign name with the variable name. There are a number of ways to go about that, though, and the best is really dependant on the particular data you're storing. I've posted examples of conversion from bioware to mysql, but I don't remember whether it was here or on the bioboards scripting forum, so you may want to search both boards.

Funky

[Spawnblade]

[Fireboar]

You don't actually - SQLExecDirect is a competent NWNX database scripter's best friend. Just use that to call SELECT, INSERT or UPDATE queries to manage rows and columns of data however you like.

To be honest, using the SetPersistent functions exclusively is a bit like seeing an ENORMOUS and delicious feast right in front of you, for you, with just about everything you could possibly want to eat, then just having a sandwich. Sure, it's nice, but you could do so much more.

[FunkySwerve]

[Spawnblade]

Thought I'd take a peek at this thread again.

Thanks for the replies, again. Spent the last 16ish hours writing up a couple thousand lines of custom functions for our database . It was pretty easy once I realized I had a pretty high level of control over the system. I really pity anyone who actually uses the bioware equivalents (the default get/setpersistents, etc..)

I am curious though, why do the strings use the SQLGetData function, but the ints and floats work through the module variables?

I wish SQL had as smooth a method of retrieving data through NWNX as it does when inputting it .

Wow talk about a learning experience though.

[Disco]

About the float/int return stuff. I think teh answer is pretty simple: an NWN function can only return one variable type, and string can represent both floats and ints, but int and float can't represent strings.