Thanks all for your suggestions, I will open respective issues for minor improvements. Also mmamkin connected with me directly and also suggested to use prefix "pg-" for whole library not only for public functions. I think that I probably should to use namespaces to hide private functions. It
+1 for writing tests.
+1 for using aw-‘s test harness.
+1 for having a sane license.
Huzzah! :)
On Tue, 15 Jan 2019 21:11 +0300, Abel Normand wrote:
> Hello everyone,
>
> I'm happy to announce that I released my small library to
> interfacing with> PostgreSQL --
> I'm happy to announce that I released my small library to interfacing with
> PostgreSQL --
> https://gitlab.com/Abel-ze-Normand/pgint.l
Tested:
centos7 psql-9.2.xx -> works
voidlinux psql-9.6.xx -> works
(mike)
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Thanks for your great job
In my opinion:
> 1) should I use PostgreSQL error codes and throw exceptions based on
them? So you could probably write:
>
> (catch 'PGintegrityError ...)
> (catch 'PGconstraintError ...)
You should.
It's a good practice to handle exceptions and this allow developers
