From: Michael Snoyman mich...@snoyman.com
I took a quick look at the enumerators library, but it doesn't seem to
have
the necessary support for handling data that comes from arbitrary C API
function calls rather than handles or sockets.
It does support this, for prior art see yaml[1]
On Tue, Jan 18, 2011 at 1:17 PM, John Lato jwl...@gmail.com wrote:
From: Michael Snoyman mich...@snoyman.com
I took a quick look at the enumerators library, but it doesn't seem to
have
the necessary support for handling data that comes from arbitrary C API
function calls rather than
On Sat, Jan 8, 2011 at 11:55 AM, Michael Snoyman mich...@snoyman.com wrote:
In general I think it would be a good thing to have solid, low-level bindings
to PostgreSQL.
Well, there is PostgreSQL and libpq on hackage:
http://hackage.haskell.org/package/libpq
On Mon, Jan 17, 2011 at 4:49 PM, Leon Smith leon.p.sm...@gmail.com wrote:
On Sat, Jan 8, 2011 at 11:55 AM, Michael Snoyman mich...@snoyman.com wrote:
In general I think it would be a good thing to have solid, low-level
bindings to PostgreSQL.
Well, there is PostgreSQL and libpq on hackage:
On 01/17/2011 10:07 AM, Michael Snoyman wrote:
On Mon, Jan 17, 2011 at 4:49 PM, Leon Smithleon.p.sm...@gmail.com wrote:
On Sat, Jan 8, 2011 at 11:55 AM, Michael Snoymanmich...@snoyman.com wrote:
In general I think it would be a good thing to have solid, low-level bindings
to PostgreSQL.
On Mon, Jan 17, 2011 at 10:52 PM, John Goerzen jgoer...@complete.org wrote:
On 01/17/2011 10:07 AM, Michael Snoyman wrote:
On Mon, Jan 17, 2011 at 4:49 PM, Leon Smithleon.p.sm...@gmail.com
wrote:
On Sat, Jan 8, 2011 at 11:55 AM, Michael Snoymanmich...@snoyman.com
wrote:
In general I
On 01/17/2011 03:16 PM, Michael Snoyman wrote:
I've brought up before my problem with the convertible package: it
encourages usage of partial functions. I would prefer two typeclasses,
one for guaranteed conversions and one for conversions which may fail.
In fact, that is precisely why
On Mon, Jan 17, 2011 at 11:38 PM, John Goerzen jgoer...@complete.org wrote:
On 01/17/2011 03:16 PM, Michael Snoyman wrote:
I've brought up before my problem with the convertible package: it
encourages usage of partial functions. I would prefer two typeclasses,
one for guaranteed conversions
On Fri, Jan 7, 2011 at 6:01 PM, John Goerzen jgoer...@complete.org wrote:
On 01/07/2011 09:49 AM, John Goerzen wrote:
On 01/07/2011 05:24 AM, Michael Snoyman wrote:
On Fri, Jan 7, 2011 at 11:44 AM, Iustin Popius...@google.com wrote:
Yes, I had a bug reported in persistent-postgresql that I
Hi all,
It seems that (at least) the postgresql bindings do not allow pure
binary data.
I have a simple table:
debug=# create table test (name bytea);
byteas seems to be the backing type on the DB side for bytestrings.
and then I run this:
import Database.HDBC.PostgreSQL
import
On Fri, Jan 7, 2011 at 11:44 AM, Iustin Pop ius...@google.com wrote:
Hi all,
It seems that (at least) the postgresql bindings do not allow pure
binary data.
I have a simple table:
debug=# create table test (name bytea);
byteas seems to be the backing type on the DB side for bytestrings.
On 01/07/2011 05:24 AM, Michael Snoyman wrote:
On Fri, Jan 7, 2011 at 11:44 AM, Iustin Popius...@google.com wrote:
Yes, I had a bug reported in persistent-postgresql that I traced back
to this bug. I reported the bug, but never heard a response. Frankly,
if I had time, I would write a low-level
On Fri, Jan 07, 2011 at 09:49:35AM -0600, John Goerzen wrote:
On 01/07/2011 05:24 AM, Michael Snoyman wrote:
On Fri, Jan 7, 2011 at 11:44 AM, Iustin Popius...@google.com wrote:
Yes, I had a bug reported in persistent-postgresql that I traced back
to this bug. I reported the bug, but never
On 01/07/2011 09:49 AM, John Goerzen wrote:
On 01/07/2011 05:24 AM, Michael Snoyman wrote:
On Fri, Jan 7, 2011 at 11:44 AM, Iustin Popius...@google.com wrote:
Yes, I had a bug reported in persistent-postgresql that I traced back
to this bug. I reported the bug, but never heard a response.
14 matches
Mail list logo