Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Bottleneck somewhere in ODBC PostgreSQL | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Base | Reporter: | Unknown <non-migrated> | ||||||
Component: | code | Assignee: | christoph.lukasiak | ||||||
Status: | CLOSED IRREPRODUCIBLE | QA Contact: | issues@dba <issues> | ||||||
Severity: | Trivial | ||||||||
Priority: | P3 | CC: | issues | ||||||
Version: | OOo 1.1 RC | ||||||||
Target Milestone: | --- | ||||||||
Hardware: | PC | ||||||||
OS: | Windows XP | ||||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||
Developer Difficulty: | --- | ||||||||
Attachments: |
|
Description
Unknown
2003-07-31 04:42:52 UTC
Created attachment 8177 [details]
The odbc log from the OOo session
Created attachment 8178 [details]
A much smaller log from a successful select, not OOo
sounds to me more like a database than an API issue 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. 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. 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 correction: winxp not linux in this case 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 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 change subcomponent to 'none' |