non-closed SQLite connections

[fielmann]

I'm using SQLite with autoit:

#include <SQLite.au3>
#include <SQLite.dll.au3>

_SQLite_Startup()
_SQLite_Open("Gala.db")

$SQL = "SELECT * FROM my_table;"

$result = _SQLite_Exec(-1,$SQL) 
if $result <> 0 then MsgBox(0,"SQL-Error","Can't execute SQL-Statement")

_SQLite_Close()     ; <- But what happens when I can't do it
_SQLite_Shutdown()

e.g. script abort abnormaly:

what happens in that case with non-closed SQLite sessions?

[KaFu]

From help-file for dllclose(), as _SQLite_Startup() does a dllopen() with some additional checks...

Upon termination, AutoIt automatically closes any dlls it opened but calling DllClose is still a good idea.

Best Regards

Edited January 13, 2009 by KaFu

[PsaltyDS]

I'm using SQLite with autoit:

#include <SQLite.au3>
#include <SQLite.dll.au3>

_SQLite_Startup()
_SQLite_Open("Gala.db")

$SQL = "SELECT * FROM my_table;"

$result = _SQLite_Exec(-1,$SQL) 
if $result <> 0 then MsgBox(0,"SQL-Error","Can't execute SQL-Statement")

_SQLite_Close() ; <- But what happens when I can't do it
_SQLite_Shutdown()

e.g. script abort abnormaly:

what happens in that case with non-closed SQLite sessions?

It's no big deal. SQLite does not have a server process that hosts "connections". It is based on simple file share with an internal file lock only while actually writing to the DB file. Everything _SQLite_Close() does is internal to your script and does not affect the state of the DB file itself.