Excerpts from Michael Glaesemann's message of vie may 20 15:07:27 -0400 2011:
>
> On May 20, 2011, at 12:51, Alvaro Herrera wrote:
>
> > Excerpts from Tom Lane's message of vie may 20 12:43:25 -0400 2011:
> >> Alvaro Herrera writes:
> >>> I was just messing around with a datatype that's based in
On May 20, 2011, at 12:51, Alvaro Herrera wrote:
> Excerpts from Tom Lane's message of vie may 20 12:43:25 -0400 2011:
>> Alvaro Herrera writes:
>>> I was just messing around with a datatype that's based in int64
>>> representation. Pretty much everything (seems to) work cleanly, but one
>>> pr
Excerpts from Tom Lane's message of vie may 20 12:43:25 -0400 2011:
> Alvaro Herrera writes:
> > I was just messing around with a datatype that's based in int64
> > representation. Pretty much everything (seems to) work cleanly, but one
> > problem I have is that I cannot build the correct CREATE
Alvaro Herrera writes:
> I was just messing around with a datatype that's based in int64
> representation. Pretty much everything (seems to) work cleanly, but one
> problem I have is that I cannot build the correct CREATE TYPE sentence
> in the .sql.in file to actually install the type, because t
Hi,
I was just messing around with a datatype that's based in int64
representation. Pretty much everything (seems to) work cleanly, but one
problem I have is that I cannot build the correct CREATE TYPE sentence
in the .sql.in file to actually install the type, because there's no
easy way to figur
