Issue 17682 - Bottleneck somewhere in ODBC PostgreSQL
Summary: Bottleneck somewhere in ODBC PostgreSQL
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: christoph.lukasiak
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-31 04:42 UTC by Unknown
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
The odbc log from the OOo session (175.01 KB, text/plain)
2003-07-31 04:44 UTC, Unknown
no flags Details
A much smaller log from a successful select, not OOo (3.96 KB, text/plain)
2003-07-31 04:47 UTC, Unknown
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-07-31 04:42:52 UTC
On a Windows XP, PostgreSQL ODBC driver 7.03.01, PostgreSQL version 7.2.1
OOo freezes.  Database connection is actually made but soon gets lost in a maze
of select statements.  The same driver, database, and indeed record (tuple) are
retrieved by a separate program with no delay.  I have corresponding odbc logs
available.
Comment 1 Unknown 2003-07-31 04:44:08 UTC
Created attachment 8177 [details]
The odbc log from the OOo session
Comment 2 Unknown 2003-07-31 04:47:18 UTC
Created attachment 8178 [details]
A much smaller log from a successful select, not OOo
Comment 3 ooo 2003-07-31 16:32:34 UTC
sounds to me more like a database than an API issue
Comment 4 Frank Schönheit 2003-08-01 07:51:53 UTC
scott, thanks for reporting this.
Please explain in more detail what you're doing (so we must not guess
from the logs :) - I can easily connect to PostgreSQL, with 7.03.01,
on WXP. So to know what you're doing different, please exactly
describe the steps to reproduce this.
If there's a special table, or some spaecial data involved, knowing
this (e.g. the table structure) would also be good.
Thanks.
Comment 5 Unknown 2003-08-01 15:20:34 UTC
In this case I am doing a simple select on a table.  I don't think the
problem is specific to the macro or the table as OOo also freezes when
viewing the data source.  This has been intermittent, though.  If the
view does display it occurs after an inordinate period of time.  The
computer I'm concerned with is a production machine and I can
generally only experiment with it after business hours, using Remote
Adminstrator.

If you compare the two ODBC logs, they start to differ at the point of
connecting to the database.  The log for the system that works does a
simple select on a user security table (I believe); the OOo log shows
a series of very convoluted selects on system tables not directly
related to my query.

Unfortunately, I think the problem stems from some specific
characteristics of this XP.  I'm hoping that this can be resolved with
some additional connection arguments.

In the macro, I set up the connection, thusly:

  rowSet = createUnoService("com.sun.star.sdbc.RowSet")
  rowSet.SetPropertyValue("DataSourceName", "AMS-wcgc_pg")

The first select statement run is:

  sql_stmt = "select cswcab from casefile where casenmbr = (select
last_case from seclogin where uname="+"'"+uName+"')"
  
  rowSet.SetPropertyValue("Command", sql_stmt)
  rowSet.execute

The macros freezes on the execute statement.
Comment 6 ocke.janssen 2003-08-04 07:40:52 UTC
Hi *,

just for the file: :-)
I'm using the PostgresSQL ODBC driver version 7.03.01.09 and the
problem of the office freeze doesn't appear.

Best regards,

Ocke
Comment 7 christoph.lukasiak 2003-10-07 10:38:42 UTC
correction: winxp not linux in this case
Comment 8 christoph.lukasiak 2003-10-13 10:32:09 UTC
CLU->scottholmes: generally works for me, too - please try to 
investigate it deeper and give a reproducable step by step 
description 

sorry, i can imagine that you have this problem, but in the current 
state your bug is not repro for me
Comment 9 christoph.lukasiak 2003-11-24 14:45:49 UTC
over one month no reaktion - not to reproduce - so i close this issue

if someone can repro that an want to add a further description, do not
hestitate to reopen this issue
Comment 10 hans_werner67 2004-02-02 12:18:05 UTC
change subcomponent to 'none'