ADO operations

ADO operations

am 22.03.2006 14:00:22 von SAFAK CIRAG

This is a multi-part message in MIME format.

------=_NextPart_000_0057_01C64DC1.57AB2A60
Content-Type: text/plain;
charset="iso-8859-9"
Content-Transfer-Encoding: quoted-printable

Hi,
I'm using psqlodbc-08_01_0200. I created a database with UTF-8 encoding. =
While inserting,updating or deleting a record, PostgreSQL Unicode Driver
returns an error : "Insufficient base table information for updating or =
refreshing". Before creating the database with UTF-8 encoding, i was =
using a database with ANSI encoding and driver as PostgreSQL ANSI. There =
is nothing wrong with ANSI side. DNSless connection string is the =
following:

"Driver=3D{PostgreSQL =
Unicode};SERVER=3Dlocalhost;PORT=3D5432;DATABASE=3Dncpgdb;UI D=3Dpostgres;=
PWD=3D*******;
=
BI=3D4;BoolsAsChar=3D1;ByteaAsLongVarBinary=3D1;CancelAsFree Stmt=3D0;Comm=
Log=3D0;Debug=3D0;
DisallowPremature=3D0;ExtraSysTablePrefixes=3Ddd_;FakeOidInd ex=3D0;
=
Fetch=3D100;Ksqo=3D1;LFConversion=3D1;LowerCaseIdentifier=3D 0;MaxLongVarc=
harSize=3D8190;MaxVarcharSize=3D254;
=
protocol=3D6.4;ReadOnly=3D0;RowVersioning=3D0;ShowOidColumn= 3D0;ShowSyste=
mTables=3D0;SSLmode=3Dprefer;
=
Optimizer=3D1;Parse=3D0;protocol=3D6.4;ReadOnly=3D0;RowVersi oning=3D0;Sho=
wOidColumn=3D0;ShowSystemTables=3D0;SSLmode=3Dprefer;
=
TextAsLongVarchar=3D1;TrueIsMinus1=3D0;UniqueIndex=3D1;Unkno wnsAsLongVarc=
har=3D0;UnknownSizes=3D0;
UpdatableCursors=3D0;UseDeclareFetch=3D1;UseServerSidePrepar e=3D0"

Should i change connection string parameters in order not to get the =
error("Insufficient base...")?
------=_NextPart_000_0057_01C64DC1.57AB2A60
Content-Type: text/html;
charset="iso-8859-9"
Content-Transfer-Encoding: quoted-printable



charset=3Diso-8859-9">




Hi,

I'm using psqlodbc-08_01_0200. I =
created a database=20
with UTF-8 encoding. While inserting,updating or deleting a record, =
PostgreSQL=20
Unicode Driver

returns an error : "Insufficient base =
table=20
information for updating or refreshing". Before creating the database =
with UTF-8=20
encoding, i was using a database with ANSI encoding and driver as =
PostgreSQL=20
ANSI. There is nothing wrong with ANSI side. DNSless connection string =
is the=20
following:

 

"Driver=3D{PostgreSQL=20
Unicode};SERVER=3Dlocalhost;PORT=3D5432;DATABASE=3Dncpgdb;UI D=3Dpostgres;=
PWD=3D*******;

size=3D2> BI=3D4;BoolsAsChar=3D1;ByteaAsLongVarBinary=3D1;CancelAsFr=
eeStmt=3D0;CommLog=3D0;Debug=3D0;

size=3D2> DisallowPremature=3D0;ExtraSysTablePrefixes=3Ddd_;FakeOidI=
ndex=3D0;

size=3D2>  Fetch=3D100;Ksqo=3D1;LFConversion=3D1;LowerCaseIdentifier=3D =
0;MaxLongVarcharSize=3D8190;MaxVarcharSize=3D254;

size=3D2> protocol=3D6.4;ReadOnly=3D0;RowVersioning=3D0;ShowOidColum=
n=3D0;ShowSystemTables=3D0;SSLmode=3Dprefer;

size=3D2> Optimizer=3D1;Parse=3D0;protocol=3D6.4;ReadOnly=3D0;RowVer=
sioning=3D0;ShowOidColumn=3D0;ShowSystemTables=3D0;SSLmode=3 Dprefer; T>

size=3D2> TextAsLongVarchar=3D1;TrueIsMinus1=3D0;UniqueIndex=3D1;Unk=
nownsAsLongVarchar=3D0;UnknownSizes=3D0;

size=3D2> UpdatableCursors=3D0;UseDeclareFetch=3D1;UseServerSidePrep=
are=3D0"

 

Should i change connection string =
parameters in=20
order not to get the error("Insufficient =
base...")?


------=_NextPart_000_0057_01C64DC1.57AB2A60--

Re: ADO operations

am 22.03.2006 16:06:22 von Ludek Finstrle

> I'm using psqlodbc-08_01_0200. I created a database with UTF-8
> encoding. While inserting,updating or deleting a record,
> PostgreSQL Unicode Driver

Do you mean you use UPDATE, INSERT and DELETE SQL statements?
Are you able to do this with psql or pgAdmin client?

> returns an error : "Insufficient base table information for
> updating or refreshing". Before creating the database with UTF-8

Please send us the mylog output with the problem.

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Re: ADO operations

am 24.03.2006 09:33:09 von Ludek Finstrle

> > returns an error : "Insufficient base table information for
> > updating or refreshing". Before creating the database with UTF-8
>
> Please send us the mylog output with the problem.

Could you try to enable Parse Statements option? Does it help?

BTW the log you sent me is long. Could you post the problemateic query?
I see no error but there could be another problem. If you send me
the query I can locate the problematic part better.

Thanks,

Luf

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Re: ADO operations

am 28.03.2006 18:51:55 von Jamal Mazrui

This error can be caused by using the adCmdTableDirect constant as the
last parameter of the Open method of a record set object. Try using
AdCmdTable instead. Also, such errors are reduced if adUseClient is
used as the cursor location instead of adUseServer.

Hope this helps,
Jamal



-----Original Message-----
From: pgsql-odbc-owner@postgresql.org
[mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Ludek Finstrle
Sent: Wednesday, March 22, 2006 10:06 AM
To: SAFAK CIRAG
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] ADO operations


> I'm using psqlodbc-08_01_0200. I created a database with UTF-8
> encoding. While inserting,updating or deleting a record,
> PostgreSQL Unicode Driver

Do you mean you use UPDATE, INSERT and DELETE SQL statements?
Are you able to do this with psql or pgAdmin client?

> returns an error : "Insufficient base table information for
> updating or refreshing". Before creating the database with UTF-8

Please send us the mylog output with the problem.

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly