Resetplugin disconnects sqlite

[highv priest]

Tested this out exhaustingly and found the cause. Whenever the server resets from the resetplugin it disconnects with sqlite... Is there a way to remedy this problem? If I manually turn off nwserver then it works fine so it's literally only that plugin.

EDIT= By disconnect I mean it deletes everything created in the database-journal instead of dumping it into the actual sqlite.db

[Terra_777]

not sure if this works for sqlite but try calling this on module load:

[highv priest]

Ok I'll try that and hopefully it works. I want to use SQL, but when you're only using it to store single instances of variables it appears sqlite is faster. I just need to make it permanently store it lol.

[highv priest]

It didn't work. This is the statement returned:

NWNX ODBC2 plugin V.0.9.2.5
(c) 2005 by Ingmar Stieger (Papillon) and Jeroen Broekhuizen
visit us at http://www.nwnx.org

o Logfile maximum size limit is: 524288 bytes
o Log level: Everything will be logged.
o Using SQLite connection.
o Hooking SCO....hooked at 5d5830
o Hooking RCO....hooked at 5d5710
o Connect successful.
o Got request: SET AUTOCOMMIT=1
! SQL Error: near "SET": syntax error

[highv priest]

I downloaded your system_data_2 plugin to see if the terminateprocess in it will allow my server to reset without breaking SQL connection, lol waiting for a natural reset to test it out.

[virusman]

Try this version
http://data.virusman.ru/nwn/nwnx_reset-0.2-win32.rar
_________________
In Soviet Russia, NWN plays you!

[highv priest]

It didn't work when I used Terra's system_data_2 to close it down :/. The automatic(and only automatic) reset still causes the sqlite to not dump the database-journal to the database.

EDIT= Virusman I originally did use that plugin, but it caused the binds to be lost as well. Is there something I'm missing that will make sqlite actually dump the journal files to database without me manually turning off nwserver?

[eeriegeek]

Last time I worked with the Linux sqlite db handler, it was explicitly beginning a transaction on initialization. This requires an explicit commit to avoid a rollback on shutdown. You could try issuing a COMMIT just before calling the reset plugin. Something like:

[highv priest]

You sir are amazing! Thank you for the assistance. Issuing the commit right before server reset does infact work to dump the journal files into the database where they belong. You said I have to issue a BEGIN statement after issuing a commit statement. Does that mean if I issue a commit statement without issuing a BEGIN afterwards it won't write any more information?

[eeriegeek]

Hey, glad it's working. Issuing a new BEGIN just opens a new transaction, it will have to be followed at some point with another COMMIT. The sqlite plugin presumably uses transactions this way for the side effect that sets of statements in a transaction run faster. If you close the current transaction with a COMMIT and continue to run SQL statements, sqlite conveniently goes into autocommit mode and wraps each statement with a transaction as needed, but this is somewhat slower.