Thread: Driver compatibility

Driver compatibility

From
Együd Csaba
Date:
Hi,
is psqlODBC v8 compatible with Postgres v7.3.2?
Can I install multiple versions of ODBC driver on the same client? I'd like
to use v7 and v8 parallel.

An application connects to postgres 7.3.2 db via odbc v7.x. Upgrading the
driver to v8 the application sends an error message that one of the fileds
can not be found.

BTW the ODBC log file shows that it recognized the field names and fetched
all the 7 records. What can be the problem.

(The client application created in Delphi7 and uses BDE 5)

Thanks,
-- Csaba Együd

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 2005.01.17.




--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 2005.01.17.


Re: Driver compatibility

From
"Trewern, Ben"
Date:
Try www.zeoslib.net if that is a possibility.  It seems to be much a more stable Delphi interface and works with both
7.xand 8.0 versions of PostgreSQL. 

Regards,

Ben


> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org]
> Sent: 19 January 2005 11:47
> To: 'Pgsql-Odbc@Postgresql.Org'
> Subject: [ODBC] Driver compatibility
>
>
> Hi,
> is psqlODBC v8 compatible with Postgres v7.3.2?
> Can I install multiple versions of ODBC driver on the same
> client? I'd like to use v7 and v8 parallel.
>
> An application connects to postgres 7.3.2 db via odbc v7.x.
> Upgrading the driver to v8 the application sends an error
> message that one of the fileds can not be found.
>
> BTW the ODBC log file shows that it recognized the field
> names and fetched all the 7 records. What can be the problem.
>
> (The client application created in Delphi7 and uses BDE 5)
>
> Thanks,
> -- Csaba Együd
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 2005.01.17.
>
>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 2005.01.17.
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)
>


***********************************************************************
This email and any attachments transmitted with it are confidential
and intended solely for the use of the individual or entity to whom
they are addressed. If you have received this email in error please
notify the sender and do not store, copy or disclose the content
to any other person.

It is the responsibility of the recipient to ensure that opening this
message and/or any of its attachments will not adversely affect
its systems. No responsibility is accepted by the Company.
***********************************************************************


Re: Driver compatibility

From
Együd Csaba
Date:
Yes I know Zeos, but I'm afraid it is too late to change to that because
this project consists of 300 forms. It would be very very painful to
rewrite...

I think there must be some way to have both versions work on the same
machine.

Bye,
  -- Csaba

-----Original Message-----
From: pgsql-odbc-owner@postgresql.org
[mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Trewern, Ben
Sent: Wednesday, January 19, 2005 1:16 PM
To: Pgsql-Odbc@Postgresql.Org
Subject: Re: [ODBC] Driver compatibility

Try www.zeoslib.net if that is a possibility.  It seems to be much a more
stable Delphi interface and works with both 7.x and 8.0 versions of
PostgreSQL.

Regards,

Ben


> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org]
> Sent: 19 January 2005 11:47
> To: 'Pgsql-Odbc@Postgresql.Org'
> Subject: [ODBC] Driver compatibility
>
>
> Hi,
> is psqlODBC v8 compatible with Postgres v7.3.2?
> Can I install multiple versions of ODBC driver on the same client? I'd
> like to use v7 and v8 parallel.
>
> An application connects to postgres 7.3.2 db via odbc v7.x.
> Upgrading the driver to v8 the application sends an error message that
> one of the fileds can not be found.
>
> BTW the ODBC log file shows that it recognized the field names and
> fetched all the 7 records. What can be the problem.
>
> (The client application created in Delphi7 and uses BDE 5)
>
> Thanks,
> -- Csaba Együd
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 2005.01.17.
>
>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 2005.01.17.
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to
> majordomo@postgresql.org)
>


***********************************************************************
This email and any attachments transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the sender
and do not store, copy or disclose the content to any other person.

It is the responsibility of the recipient to ensure that opening this
message and/or any of its attachments will not adversely affect its systems.
No responsibility is accepted by the Company.
***********************************************************************


---------------------------(end of broadcast)---------------------------
TIP 3: 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

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 2005.01.17.




--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 2005.01.17.


Re: Driver compatibility

From
"Merlin Moncure"
Date:
> Yes I know Zeos, but I'm afraid it is too late to change to that because
> this project consists of 300 forms. It would be very very painful to
> rewrite...
>
> I think there must be some way to have both versions work on the same
> machine.
>
Yes.  Zeos and BDE can't share the same connection object, but they can share everything else.  For example, you can
swapout a dataset (ZDataset for TBDEDataset) and as long as the field names are the same, it should work the same.  You
canmix/match different types of connections on the same app or even on the same form. 

I was not aware you were using Delphi: your connection accumulation problem might be because of the bde.  The bde sits
betweenthe database/odbc and your app and is buggy.  It has been known to do things like open connections and not close
them. Zeos communicates directly to postgres and bypasses both the BDE and ODBC layers.  Of course, if you have a 3rd
partyMFC ODBC based library, it is not going through the BDE. 

Unfortunately, I think you are going to have problems until you replace the BDE, either with Zeos or something
else...thisis the hard lesson that many Borland developers have to learn. 

For a short term fix I would:
1. Turn statement level statistics on
2. configure postgres to reserve at least one connection for the superuser.  Make you're your applications are not
loggingin as a superuser. 
3. Create a small app that queries pg_stat_activity (and logs on as superuser)...if connections are still high, start
killingthem based on last activity.  There is a backend function to do this, pq_kill_backend_pid or something like
that.

For a longer term fix:
1. Move away from BDE.  This is easier than you might think.  You can do it gradually.
2. Construct an odbc test app (written in C) that demonstrates your problem.  This will be a big help in getting it
fixed,if it is odbc-specific. 
3. Determine which process is holding the connections.  Believe me, there is one.

Good luck!
Merlin