Ugh... statically alocated buffer and sprintf()s with data of variable
length; usage of data as format string... hell, i'm happy this is code
for win32, although it scares me greatly. will it go as it is to PGSQL?
:-0
On Tue, Jul 17, 2001 at 12:12:48AM +0200, Darko Prenosil wrote:
> Hi ,Bruce !
>
> Ugh... statically alocated buffer and sprintf()s with data of variable
> length; usage of data as format string... hell, i'm happy this is code
> for win32, although it scares me greatly. will it go as it is to PGSQL?
> :-0
Good points. Right now, because they arrived on the same day, we have
I want to add some data using Copy from command
how to do it
i have following table etc..
CREATE TABLE "buyers" ( "id" int4 DEFAULT
nextval('buyers_pk_seq'::text) NOT NULL, "fk_partnerid" int4 DEFAULT
'0' NOT NULL, "username" character varying(20) DEFAULT 'luser' NOT
NULL, "password"
Hi ,Bruce !
There is diff for fe-connect.c.
Diff was made with options -cr as You asked.
I must say that this is the first time I ever use diff, so I do not know if
if it is ok.
I did not check if all of non-blocking functions are working,
but I checked PQsetnonblocking,PQisnonblocking,
PQsendQue
I just got a new Win32 libpq patch. Please see it at:
http://candle.pha.pa.us/cgi-bin/pgpatches
How does your match with that one? I haven't applied it yet.
> Hi ,Bruce !
> There is diff for fe-connect.c.
> Diff was made with options -cr as You asked.
> I must say that this is the f
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
This must be merged with the other Win32 libpq patch. Thanks.
> Hi ,Bruce !
> There is diff for fe-connect.c.
> Diff was made with options -cr as You asked.
> I must say tha
Rainer Mager ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
some timestamps are wrong from JDBC
Long Description
Postgres 7.1 (or its driver) munges timestamps.
When the milliseconds M are in the range:
0 < (M mod 1000) < 1
