On 2017-07-07 12:54:33 +0200, Michael Meskes wrote:
> > Some people use http://libpqtypes.esilo.com/
>
> Never before saw this. It does not seem to have more in common than the
> name, though.
It has binary to text conversion functionality for various types. I
don't exactly know what Kaare needs,
I agree with Michael Meskes that duplicating the code is probably not a good
idea. Now I see other rust crates just depend on the right libraries to be
installed by the developer, so I'll punt the problem until it bites me for
real.
This confuses me, though
> Indeed. I'm quite strongly against
> Indeed. I'm quite strongly against exposing / using pgtypeslib in more
> places. If anything it should be phased out. Because that code is
Feel free to come up with a replacement. :)
> definitely not always kept up2date, and it's a lot of work to do so. If
> anything the code should be rewritt
Hi,
On 2017-07-06 20:26:29 +0200, Michael Meskes wrote:
> > But is this possible, or feasible? I see that the makefile refers to
>
> Possible yes, but in general I'm not a big fan of duplicating code. I
> spend too much time to keep those copies in sync.
Indeed. I'm quite strongly against expos
> But is this possible, or feasible? I see that the makefile refers to
Possible yes, but in general I'm not a big fan of duplicating code. I
spend too much time to keep those copies in sync.
> Makefile.global, and also includes stuff from ecpg, aat least. I don't want
> to
Yes, but these shou
Hi
For learning purposes (and because I probably need it) , I've started to make
Rust bindings to the pgtypes Library.
One problem I'm thinking about right now is how to know if, and where, the
library and the include files are installed. One way to avoid that problem is
to include the source
