Обсуждение: ODBC Problem

Поиск
Список
Период
Сортировка

ODBC Problem

От
Jamz@AirNet.Com.AU
Дата:

Greetings people,

            Before I go nuts, I wonder if anyone has solved this problem before; I have been using the ODBC driver for our Postgres server to develop software in Visual Basic with great success until just recently.

 

Symptoms of the problem are that queries on some machines execute correctly, but taking the same code and executing it on another machine returns empty recordsets.  I made sure all the drivers were the same and that the latest MDAC 2.7 was installed on all machines.

 

On further investigation, I found that on the affected machines, queries to tables with an index come back with an empty recordset.

 

Win2k Terminal Server SP2: okay - queries return data

WinXP Beta2: okay - queries return data

WinNT4 Server: only queries on some tables return data

Win2k Server SP2: only queries on some tables return data

 

I guess this must be something to do with the setup of the ODBC driver on these machines, but I can't for the life of me find any difference in settings.  All the machines use identical connect strings.

 

I looked at the ODBC logs to find something that was failing and couldn't really see any thing bad:

 

conn=35795448, SQLDriverConnect(out)='DRIVER={PostGreSQL};DATABASE=bmf;SERVER=bm

f.some.domain;PORT=5432;UID=postgres;PWD=xxxxx;READONLY=0;PROTOCOL=6.4;FA

KEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS='

conn=35795448, query='SELECT * FROM userservices WHERE printform=true AND formpr

inted IS NULL'

    [ fetched 1 rows ]

conn=35795448, SQLDisconnect

 

So it looked like the row I wanted was retrieved but the recordset still remained empty L

 

I believe the server is running Postgres 7.0.3 :

 

[root@bmf bin]# ./psql -V

psql (PostgreSQL) 7.0.3

contains readline, history support

Portions Copyright (c) 1996-2000, PostgreSQL, Inc

Portions Copyright (c) 1996 Regents of the University of California

Read the file COPYRIGHT or use the command \copyright to see the

usage and distribution terms.

 

All machines are using the same ODBC driver version 6.5, PSQLODBC.DLL 4/2/2000

 

If anyone knows if there is a known problem with this combo please let me know and I will have a case to get the admin to upgrade.

 

Cheers & TIA,

            Jamz.

 

 

 

=-=-=-=-=-=-=-=-=-=-=-=-

"We should have laser guns!"

      - Andrew Hill (Post Support Call)

 

RE: ODBC Problem

От
"Henshall, Stuart - WCP"
Дата:
It may well be worth trying the latest version of the driver (Have a look at
http://odbc.postgresql.org , or
http://www.ca.postgresql.org/ftpsite/odbc/versions/full/)
Also there is an postgreSQL ODBC specific list: pgsql-odbc@postgresql.org
- Stuart

> -----Original Message-----
> From:    Jamz@AirNet.Com.AU [SMTP:Jamz@AirNet.Com.AU]
> Sent:    Wednesday, July 18, 2001 1:11 AM
> To:    pgsql-interfaces@postgresql.org
> Subject:    ODBC Problem
> 
> Greetings people,
>             Before I go nuts, I wonder if anyone has solved this problem
> before; I have been using the ODBC driver for our Postgres server to
> develop software in Visual Basic with great success until just recently.
>  
> Symptoms of the problem are that queries on some machines execute
> correctly, but taking the same code and executing it on another machine
> returns empty recordsets.  I made sure all the drivers were the same and
> that the latest MDAC 2.7 was installed on all machines.
>  
> On further investigation, I found that on the affected machines, queries
> to tables with an index come back with an empty recordset.
>  
> Win2k Terminal Server SP2: okay - queries return data
> WinXP Beta2: okay - queries return data
> WinNT4 Server: only queries on some tables return data
> Win2k Server SP2: only queries on some tables return data
>  
> I guess this must be something to do with the setup of the ODBC driver on
> these machines, but I can't for the life of me find any difference in
> settings.  All the machines use identical connect strings.
>  
> I looked at the ODBC logs to find something that was failing and couldn't
> really see any thing bad:
>  
> conn=35795448,
> SQLDriverConnect(out)='DRIVER={PostGreSQL};DATABASE=bmf;SERVER=bm
> f.some.domain;PORT=5432;UID=postgres;PWD=xxxxx;READONLY=0;PROTOCOL=6.4;FA
> KEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTIN
> GS='
> conn=35795448, query='SELECT * FROM userservices WHERE printform=true AND
> formpr
> inted IS NULL'
>     [ fetched 1 rows ]
> conn=35795448, SQLDisconnect
>  
> So it looked like the row I wanted was retrieved but the recordset still
> remained empty :-(
>  
> I believe the server is running Postgres 7.0.3 :
>  
> [root@bmf bin]# ./psql -V
> psql (PostgreSQL) 7.0.3
> contains readline, history support
> Portions Copyright (c) 1996-2000, PostgreSQL, Inc
> Portions Copyright (c) 1996 Regents of the University of California
> Read the file COPYRIGHT or use the command \copyright to see the
> usage and distribution terms.
>  
> All machines are using the same ODBC driver version 6.5, PSQLODBC.DLL
> 4/2/2000
>  
> If anyone knows if there is a known problem with this combo please let me
> know and I will have a case to get the admin to upgrade.
>  
> Cheers & TIA,
>             Jamz.
>  
>  
>  
> =-=-=-=-=-=-=-=-=-=-=-=-
> "We should have laser guns!"
>       - Andrew Hill (Post Support Call)
>  


RE: ODBC Problem

От
László Tibor
Дата:
I had a same problem with Win98SE. Some of our datasets showed wrong empty recordsets using C++Builder executable with ODBCExpress components and the latest driver. But after installed a newer MDAC (2.5 I think) it dissapeared. I didn't tried the latest MDAC.
 
So nothing useful for you :-(

Tibor Laszlo
ltibor@mail.tiszanet.hu

-----Original Message-----
From: pgsql-interfaces-owner@postgresql.org [mailto:pgsql-interfaces-owner@postgresql.org]On Behalf Of Jamz@AirNet.Com.AU
Sent: Wednesday, July 18, 2001 2:11 AM
To: pgsql-interfaces@postgresql.org
Subject: [INTERFACES] ODBC Problem

Greetings people,

            Before I go nuts, I wonder if anyone has solved this problem before; I have been using the ODBC driver for our Postgres server to develop software in Visual Basic with great success until just recently.

 

Symptoms of the problem are that queries on some machines execute correctly, but taking the same code and executing it on another machine returns empty recordsets.  I made sure all the drivers were the same and that the latest MDAC 2.7 was installed on all machines.

 

On further investigation, I found that on the affected machines, queries to tables with an index come back with an empty recordset.

 

Win2k Terminal Server SP2: okay - queries return data

WinXP Beta2: okay - queries return data

WinNT4 Server: only queries on some tables return data

Win2k Server SP2: only queries on some tables return data

 

I guess this must be something to do with the setup of the ODBC driver on these machines, but I can't for the life of me find any difference in settings.  All the machines use identical connect strings.

 

I looked at the ODBC logs to find something that was failing and couldn't really see any thing bad:

 

conn=35795448, SQLDriverConnect(out)='DRIVER={PostGreSQL};DATABASE=bmf;SERVER=bm

f.some.domain;PORT=5432;UID=postgres;PWD=xxxxx;READONLY=0;PROTOCOL=6.4;FA

KEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS='

conn=35795448, query='SELECT * FROM userservices WHERE printform=true AND formpr

inted IS NULL'

    [ fetched 1 rows ]

conn=35795448, SQLDisconnect

 

So it looked like the row I wanted was retrieved but the recordset still remained empty L

 

I believe the server is running Postgres 7.0.3 :

 

[root@bmf bin]# ./psql -V

psql (PostgreSQL) 7.0.3

contains readline, history support

Portions Copyright (c) 1996-2000, PostgreSQL, Inc

Portions Copyright (c) 1996 Regents of the University of California

Read the file COPYRIGHT or use the command \copyright to see the

usage and distribution terms.

 

All machines are using the same ODBC driver version 6.5, PSQLODBC.DLL 4/2/2000

 

If anyone knows if there is a known problem with this combo please let me know and I will have a case to get the admin to upgrade.

 

Cheers & TIA,

            Jamz.

 

 

 

=-=-=-=-=-=-=-=-=-=-=-=-

"We should have laser guns!"

      - Andrew Hill (Post Support Call)

 

test blob on microsoft SQl Server 7.0

От
Manika Dey
Дата:
Hi, I have been able to transfer large data  files of size for about more than 5MB   on postgresql database , i want to
dothe same transfer of data files to database on microsoft SQl Server 7.0 can any one provide me with samples or good
document, that can help to transfer large data files to microsoft SQl Server 7.0.
 

looking forward for reply.
manika


-------------------------------------------------------------------

From:-                          | Ms. Manika Dey.                |Ph.No:--Engineer-SC (Comp. Tech.)      | IPR -- 079 -
3269276I.P.R                          |          EXT 336,315BHAT, GANDHINAGAR              | Residence -- 079 -
6873114Gujrat-- 382 428              | FAX --- 3269017
------------------------------------------------------------------