I think native SQL support is a really great thing. I prefer PostgreSQL,
so I might jump in in that area.
I feel strongly, though, that a keyed file system that works more native to
APL would be an important thing. Perhaps it can be built on top of what
you are doing - perhaps along the lines of
Hi Elias,
thanks, fixed in SVN 199.
/// Jürgen
On 04/11/2014 09:28 AM, Elias Mårtenson wrote:
After the rewrite of the native library loading, the error reported by
dlerror() is no longer included in the )MORE message. Instead, it
simply says that the file was not found.
Regards,
Elias
I'm following up to myself here.
I would like to have some advice from you guys about the design of the API.
Currently, the API for select and update is the following:
*database_id* FN '*statement*' [*argument* ...]
In other words, the first element of the ravel of the right-hand argument
is t
I've been working on an SQL interface, and right now I'm at the point where
basic SQLite support works. Here's an example:
⍝ Load the native library
* '/home/emartenson/prog/apl-sqlite/lib_sqlite.so' ⎕FX 'SQL'*
SQL
⍝ Open the SQLite database in the file /tmp/foo
*db ← SQL[1
After the rewrite of the native library loading, the error reported by
dlerror() is no longer included in the )MORE message. Instead, it simply
says that the file was not found.
Regards,
Elias
