Closed fxfactorial closed 8 years ago
Regarding gtk see https://github.com/mmottl/postgresql-ocaml/pull/17
I'm afraid, but GTK does not seem to be particularly stable right now. There isn't much I can do about that.
What concerns connection strings, it really depends on the version of your server software whether it will interpret URIs. If your PostgreSQL server is >= 9.2 it will, otherwise only keyword bindings will do. See: http://www.postgresql.org/docs/9.4/static/libpq-connect.html#LIBPQ-CONNSTRING
@mmottl yes, I am on 9.4, hence assumed that postgresql://....
would work.
@fxfactorial The OCaml bindings should pass on connection strings verbatim. I'm not sure what would happen if either the client library or server were outdated. I would assume, too, that URIs should otherwise work, but I cannot test this right now. Please let me know in case you find an issue with the bindings.
Thank you for this awesome work!
I am getting a seg fault on OS X for the prompt_gtk.ml example on OS X.
On
OS X 10.11.3, ocaml version 4.02.3, postgresql 9.5.1
installed via brew.I added
#require "posgresql, lablgtk2"
to the top and ran withutop prompt_gtk.ml host=localhost
Then I get a seg fault
after these messages:
Should I not be using
lablgtk
on OS X and instead be using the osx special gtk package?Also, can you provide an example of what a connection string for these bindings out to look like? I tried using strings of form:
postgresql://something...:some_port
but it was rejected, something more meaty than just connecting to localhost would be greatly appreciated.