Still wrong

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
Post Reply
Tommy

Still wrong

Post by Tommy » Fri 17 Jun 2005 08:58

I used new version 2.10.7 .
But still wrong value .

It garbles sometimes. (not always)

ex)
Dim dbCmd As New CoreLab.PostgreSql.PgSqlCommand
dbCmd.CommandText = "SELECT MAX(PERSON_ID) FROM TBL_PERSON ;"
dbCmd.ExecuteScalar()
The answer is '001'. but dbCmd.ExecuteScalar() answer '001x'.

postgreSQL 8.0.2 encoding:EUC_JP

Yuri
Posts: 140
Joined: Mon 08 Nov 2004 12:07

Still wrong

Post by Yuri » Fri 17 Jun 2005 09:07

Please send us script to create "TBL_PERSON" table.

Guest

Post by Guest » Fri 17 Jun 2005 10:33

This is Create table SQL.

CREATE TABLE TBL_PERSON (
USER_ID VARCHAR(10),
PERSON_ID VARCHAR(10),
KIND_CD VARCHAR(10),
TIMEZONE_CD INT DEFAULT 0,
SEQ INT DEFAULT 0,
LAST_NAME VARCHAR(50),
FIRST_NAME VARCHAR(50),
LAST_NAME_KANA VARCHAR(50),
FIRST_NAME_KANA VARCHAR(50),
DEPT VARCHAR(100),
TEL VARCHAR(50),
FAX VARCHAR(50),
E_MAIL VARCHAR(255),
NOTES TEXT,
CREATE_DATE TIMESTAMP,
CREATOR VARCHAR(50),
UP_DATE TIMESTAMP,
UPDATER VARCHAR(50),
DEL_DATE TIMESTAMP,
PRIMARY KEY (USER_ID,PERSON_ID,KIND_CD,TIMEZONE_CD)
);


'0001' is OK. But '001' is wrong.('001x')

Yuri
Posts: 140
Joined: Mon 08 Nov 2004 12:07

Post by Yuri » Fri 17 Jun 2005 11:21

Could you get '001x' using another tools, for example PgAdmin?

Tommy

Post by Tommy » Tue 21 Jun 2005 01:46

PgAdminIII is no problem.
It operates normally.

Yuri
Posts: 140
Joined: Mon 08 Nov 2004 12:07

Post by Yuri » Thu 23 Jun 2005 08:50

We can not reproduce the problem. Please specify after what actions do you get the corrupted values.
Probably problem is not in getting data but in inserting data in to the table.
Please check with PgAdmin the table contents as soon as you get wrong values with PostgreSQLDirect .NET.

Post Reply