NWNX ODBC2 object storage engine

[Papillon]

I can only speak for myself: Personally, I will not be able to port this over to Linux. The amount of resources the windows version and everything else surrounding NWNX needs is high enough as it is.

I am guessing that someone will step forward and do the port, as it was the case with the previous releases of NWNX. The only challenge would be to find the SCO/RCO functions in the linux server (not to hard with some advice) and to write the assembler code that does the hooking.
_________________
Papillon

[dguntner]

Well I, for one, am sincerely hoping that someone (Plasma John? Tenkawa? Someone else?) will do so. If I knew C well enough, I'd jump at it. Problem is, I know it well enough to basically follow what's going on, but not well enough to actually modify something from one platform to another. And assembly is right out.

--Dave (Keeping fingers crossed)

[Kosmous]

anyone tried editing the object file stored in the blob field and then retrieving it?

[Kosmous]

just tried messing with the blob entries and it wasnt causing any problems unlike when editing bioware db. Anyone else planning to do the arduous task of making SQL queries to edit the blob file via NWNX? Otherwise im gonna have to isolate certain "set in stone" properties like creature names (im assuming this hasnt been done yet for creatures). Wonder what other properties would be worth manipulating?

[Blacksting]

This is where Leto steps in. I have been modifying creature names (and EVERYTHING else) with the LetoScript.dll for almost 6 months now. Once Dragonsong sets his sights on incorporating his GFF editing code in to the new odbc plugin all will be right in NWNville.... but it is already possible now. The one thing about "hooking" this information directly that most people do not know is that it has problems with the whole multi-player server/client update scheme. The only confident way to make sure your changes are accepted by the server and other clients is a "copy and modify" like we Leto-ers are doing now. When the engine sees the "new" object everyone is notified while direct memory changes to objects via a hook need some kind of "prodding" like a transition to be crossed.

[Orleron]

I can say on pretty good authority that PlasmaJohn will not likely be doing the port to LINUX. He's got a lot of other stuff on his plate.
_________________
____________________
Blackdagger: The World of Avlis
http://www.avlis.org

The Confederation of Planes & Planets
"Go anywhere. Do anything."
http://www.copap.org

[dguntner]

Well I can always hope....

--Dave

[Trelantris]

Ok, perhaps I'm not as smart as I though. Having issue using the new ODBC. I put in the new system, modified the INI files but don't seem to be having any luck connecting to the DB, even with the demo Module. I'm using MySQL as the back end Database, and after using the create DB sign, it says it's created, but no new table shows up in the DB. The store says it's working, but the retrieve returns 0 items. (with the Object storage) I know I'm missing something...

[Gibmeat]

Somebody hook me up with the source code so I can work on the Linux port!

[Manuel]

[JeroenB]

[Papillon]

[Kosmous]

i also tried the demo module which creates the sample pwobject table. It seems something is wrong with the syntax of the SQL statement (maybe not just correct with mysql in particular). I tried my own SQL queries and it works like a charm.

[Papillon]

Please be more specific an add the corresponding nwnx_odbc.txt entries, otherwise I will not be able to help you.
_________________
Papillon

[Blacksting]

The odbc source is notably absent for the 2.60 release of the main program. This means it is still not possible to recompile the odbc plugin (for those of us outside the walls of NWNX official development land.) Was the lack of source intentional?