To connect to a Postgres database, simply use "postgresql" as the left-side argument to SQL∆Connect. The right-hand argument should be a connect string as described here: http://www.postgresql.org/docs/9.3/static/libpq-connect.html#LIBPQ-CONNSTRING
Regards, Elias On 10 July 2014 10:44, David B. Lamkins <dlamk...@gmail.com> wrote: > I'm certainly willing to consider alternatives. IIUC, lib_sql also > supports PostgreSQL. Anything else? > > How do I tell lib_sql to use a PostgreSQL server? > > The argument in favor of SQLite, of course, is that it's serverless. No > additional setup (beyond the installation of the library) required. > > Would there be any additional benefits or concerns when connecting to a > PostgreSQL server? > > As you've no doubt noticed, there's nothing in the code (or in the > standard API) to acknowledge or support the notion of multiple users. > Again: point in favor of SQLite... > > > On Thu, 2014-07-10 at 10:25 +0800, Elias Mårtenson wrote: > > I was looking at your code, and I noticed that it's SQLite-specific. > > WOuldn't it make sense to make it SQL-implementation-agnostic? > > > > > > Based on what I can see, the only SQLite-specific SQL you have in > > there is "replace into" which I had never heard about before. > > > > > > Regards, > > Elias > > > > > > On 9 July 2014 01:22, David Lamkins <da...@lamkins.net> wrote: > > I haven't yet written test scripts, but I've informally tested > > all of the functions and am reasonably confident that the > > component file API is complete and correct. > > > > > > If you'd like to try out the API while I'm working on scripted > > test cases, the repo is: > > > > https://github.com/TieDyedDevil/iso-apl-cf > > > > > > You'll find documentation is in the comments and in Annex A of > > the ISO 13751 standard. > > > > > > The standard "specifies a minimal set of functions which a > > conforming implementation must provide"; I've implemented all > > of these. I've also added several useful functions not > > mentioned in the standard, including component inquiry, > > component drop, and transaction support. > > > > > > > > Note that the code is not packaged for my package manager; I > > assume that the component file implementation would become an > > L3 library in the event it's adopted for inclusion in GNU APL. > > > > > > Júergen, I've specified the GPLv3 license since that's what > > GNU APL uses. If there's a more appropriate choice of license > > for this library, please let me know. > > > > -- > > "The secret to creativity is knowing how to hide your > > sources." > > Albert Einstein > > > > > > http://soundcloud.com/davidlamkins > > http://reverbnation.com/lamkins > > http://reverbnation.com/lcw > > http://lamkins-guitar.com/ > > http://lamkins.net/ > > http://successful-lisp.com/ > > > > > > >
