ODBC Driver
am 19.04.2010 05:02:22 von goutham jalakam--e0cb4e887bb19429db04848e308e
Content-Type: text/plain; charset=ISO-8859-1
Hello PGSQL Team,
We have a serious problems changing the driver from postgresql to
postgresql unicode.
We are using postgre sql DB since long time.
There is a requirement for our application to insert Latin chars into
postgre. So, Changed driver from PostgreSQL to *PostgreSQL** UNICODE.*
There are quite a few issues occuring using this driver.
Issue 1: When we mention *BoolsAsChar**=1* in connection string, its
returning empty value instead of 1 or 0 based on true or false.
Issue 2: we are trying to fill dataset through OdbcDataAdapter.
Code Snippet:
OdbcDataAdapter odbcAdapt = new
OdbcDataAdapter("Select * from table1;"+ "Select * from table2;" ,
cdbConn.Conn);
odbcAdapt .Fill(dataset)
always dataset is returning 0 tables.
Can you please help us. If we change the driver from postgresql unicode to
postgresql will there be much differences in the behavior?
Please previous your valuable inputs.
Regards
Goutham J
--e0cb4e887bb19429db04848e308e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
=A0PGSQL Team,
ave a serious problems changing the driver from postgresql to postgresql un=
icode.
using postgre sql DB since long time.
is a requirement for our application to insert Latin chars into postgre. So=
, Changed driver from PostgreSQL to PostgreSQL UNI=
CODE.
are quite a few issues occuring using this driver.
BoolsAsChar=3D1 in connection string, its=
returning empty value instead of 1 or 0 based on true or false.=A0<=
/div>
fill dataset through OdbcDataAdapter.
=A0
=A0 Code Snippet:
=A0 OdbcDataAda=
pter odbcAdapt =3D new OdbcDataAdapter("Select * from table1;"+ &=
quot;Select * from table2;" , cdbConn.Conn);
odbcAdap=
t .Fill(dataset)
ng 0 tables.
f we change the driver from postgresql unicode to postgresql will there be =
much differences in the behavior?
able inputs.
--e0cb4e887bb19429db04848e308e--