pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Byron Nikolaidis <byron.nikolaidis@home.com>
To: Louis Bertrand <louis@bertrandtech.on.ca>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] weird Access problem
Date: Mon, 22 Nov 1999 19:22:10 -0500
Message-ID: <3839DE32.2E7C57AB@home.com> (raw)
References: <Pine.BSO.4.10.9911220134090.19087-100000@tronix.bertrandtech.on.ca>



Louis Bertrand wrote:
> 
> Hello all,
> 
> I connect to a postgresql database from MS Access and I see some weird
> things in the postgresql log in C:\psqlodbc_XXX.log. I am using an Access
> form to enter data into a table, and the sql log has these insane long
> lines with repeated OR terms:
> 
>  conn=43911292, query='SELECT "SystemID","MailingListID","SystemType"
> FROM "Systems"  WHERE "SystemID" = 'system5' OR "SystemID" = 'System34' OR
> "SystemID" = 'System34' OR "SystemID" = 'System34' OR "SystemID" =
> 'System34' OR "SystemID" = 'System34' OR "SystemID" = 'System34' OR
> "SystemID" = 'System34' OR "SystemID" = 'System34' OR "SystemID" =
> 'System34''
>    [ fetched 2 rows ]
> 
> Access freezes up (Task not responding, ctrl-alt-del > "End task" works)
> if I keep working after this starts happening.
> 
> Using Access97 SR-1 on Win95 with iodbc 6.40.0007. The tables in Access
> are "linked" to those in pgsql via a system DSN. PostgreSQL is running on
> OpenBSD 2.6.
> 
> Is this a problem with Access or with the way I'm using the connectivity?
> I'm not a guru; I'm just trying to set up a simple demo and I'd rather it
> didn't crash while I'm running it.
> 

Actually, even though the above syntax seems odd, it is correct.  Access
uses the JET database engine, which creates keyset queries like this. 
It fetches 10 rows at a time (if you notice there are 10 terms in that
query.)   The repeats are there because the query always has the same
number of terms, and if there are less than 10 rows in this particular
keyset, it repeats them.

It shouldn't crash however.  Do you have a *unique* index on the term in
the keyset (SystemID)?  

The other thing to try is changing the driver option "use
declare/fetch".  Sometimes having this option enabled can cause things
to lock up.

Byron



view thread (2+ messages)

Message-ID: <3839DE32.2E7C57AB@home.com>
Permalink:  ../3839DE32.2E7C57AB@home.com/
Also on:    postgresql.org/message-id/3839DE32.2E7C57AB@home.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: byron.nikolaidis@home.com, louis@bertrandtech.on.ca
  Subject: Re: [INTERFACES] weird Access problem
  In-Reply-To: <3839DE32.2E7C57AB@home.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox