Just a reminder, there still doesn't appear to be a 7.3.1 tag.
This is from the "HISTORY" file.
symbolic names:
REL7_3_STABLE: 1.182.0.2
REL7_2_3: 1.153.2.8
REL7_2_STABLE: 1.153.0.2
REL7_2: 1.153
Notice 7.3 stable but nothing about 7.3.x! I also see a 7.2.3, etc
Hi Palle,
Between 7.2 and 7.3 there was an API change to the pgnotify(?) struct or
something. When 7.3 was released, we forgot to bump the version number, so
we're doing it now. It was something of an oversight, but it really needed
to be done.
There have been HEAPS of security fixes between 7.
Hi!
subject says it all, I guess. There is hardly no difference between 7.3
libpq and 7.3.1 libpq. Why the version shift? Isn't the only thing
rectifying a version shift that there is a change in the API. Maybe there
is a change, but I cannot find it.
One of the reasons I ask is, if it is a go
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> I'm using copy to import a table. I use PQescapeString() to make
> it safe, but it seems to have a problem when there is a ' in it.
PQescapeString is not designed to escape data for COPY, and will not
do the right thing. Quoting ' is not needed for COPY;
I'm using copy to import a table. I use PQescapeString() to make
it safe, but it seems to have a problem when there is a ' in it.
The column that is being copy is a varchar. If the string that
is being copied is the size of the varchar, and the string
contains a ', I get an error that the string
Tom Lane wrote:
> > Okay. But then doesn't it make sense for FETCH to fetch the contents
> > of the row (and subsequent requested rows) that the cursor is
> > currently on *then* move, and not the other way around?
>
> No, because WHERE CURRENT OF operates on the row last returned by FETCH,
> acc
Hi all,
I've recently started using Postgresql and am impressed with how
complete an RDBMS system it really is. It seems that while some
corporations may balk at using it for day to day operational use,
bringing in PGSQL for a more niche use will allow many professionals to
see its potential.
One
