From: | "Dong, Meng" <eddy(at)securities(dot)com> |
---|---|
To: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | 'int8' is not always OK, 'bigint' seems to be more reliable instead. |
Date: | 2001-07-27 01:14:58 |
Message-ID: | NHEKJKOKOJFOJLPMNIFKGEFMCCAA.eddy@securities.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Dear Bug Killer,
I have a bug to report.
As we know, for PostgreSQL, the data type 'bigint' can also be called 'int8'. Ideally, they should be identical.
But, when I create a table called XXX, if I define a column's type as 'bigint', it's Okay. Otherwise, if I choose 'int8' instead, when I try to make use of the command,
copy XXX from SOURCEFILE
it will always fail, telling me that
"RROR: copy: line 1, Bad int8 external representation "xxxxxxxxxxx
Would this be revised?
thanks and regards,
Eddy
Formatter/Programmer,
Internet Securities Inc. China (ISI)
Rm 202, Bright China Chang An Bldg.
7 Jian Guo Men Nei Ave.
Beijing 100005, China
Tel: 8610-65102596#15
Fax: 8610-65102597
E-mail: eddy(at)securities(dot)com
A Euromoney Institutional Investor Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-07-29 19:39:29 | Re: HELP! BUG? pg_dump mucks up grant/revoke |
Previous Message | And. Andruikhanov | 2001-07-25 11:21:05 | Re: timestamp (minor bug) |