I have put the SQLite addon and the e beta 807 build through a good test. I
used it to build a cross-reference
database of my online images. This involved creating a SQLite db from j,
reading a large 400 mb Thumbsplus SQLite db,
making numerous column inserts, and executing some updates as well.
Basically, things work well with one exception. Use of the sqlparm command
can leave SQLite databases open.
When this happens sqlreset_psqlite_ no longer works and you have to
terminate the J session to release the SQLite db.
I haven't been able to create a simple test case that illustrates this
behavior. Perhaps someone more familiar
with the addon code can look at these expressions and reproduce the issue.
sqlparm followed the SQL building command that replaced it. You are
generally
advised not to pass parameters by generating SQL for web apps.
NB. use of sqlparm sometimes leaves databases open
NB. dat=. sqlparm__x LocalFile_sql;SQLITE_TEXT_psqlite_;y
NB. used this instead
sql=. ('/?/''',y,'''') changestr LocalFile_sql
dat=. sqldict__x sql
NB. WARNING: this method leaves (mirror.db) open despite
NB. being closed in all cases - this is not a problem when
NB. run from (buildmirror.bat) that terminates the entire
NB. process and closes (mirror.db).
NB. rc=. sqlparm__dt UpdateLocalPresent_sql;SQLITE_TEXT_psqlite_;ak
NB. SQL statement used in place of sqlparm
sql=. UpdateLocalPresent_sql,'(',(}.;',' ,&.> quote&.> bok#AlbumKey),')'
--
John D. Baker
[email protected]
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
