Let's consider interrogating the database with a select query. The DLL would post the result in memory, where it can be read by J one cell at a time, whereas calling sqlite3.exe would either mean parsing the result posted by the process, or piping it further to a file, then read and parse that. Seems to me like using the DLL is saving me a costly step.
Unless you mean some other way? In which case I apologise for misunderstanding and must ask you for further information. As for why the 'data\sqlite' package goes this way, I guess the author will have an answer. Martin Pelletier On 2010-08-04 11:31, David Ward Lambert wrote: > Please explain reasons for choosing the dll rather than piping sql > commands to a sqlite3 process? Thanks, Dave. > > >> Date: Wed, 04 Aug 2010 09:55:04 -0400 >> From: Martin Pelletier<[email protected]> >> Subject: [Jprogramming] SQLite3 and J602a 64bits >> To: 'Programming forum'<[email protected]> >> Message-ID:<[email protected]> >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >> Greetings. >> >> I seem unable to send commands to sqlite3.dll, whether by hand or w/ >> the "data/sqlite" package. Both return domain errors on cd. >> > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
