To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=116801 Issue #|116801 Summary|Postgresql SDBC Driver Heuristics for detecting primar |y key don't work Component|Database access Version|OOO330m9 Platform|All URL| OS/Version|Linux Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|none Assigned to|dbaneedsconfirm Reported by|domcoop
------- Additional comments from [email protected] Fri Feb 4 11:36:54 +0000 2011 ------- When using the PostGresql SDBC Driver, the driver does not recognise the primary key, and then fails when using an updateable resultset. This is despite:- (1) There being a primary key on the table. (2) The primary key being included in the select statement. (3) The driver (seeming) to recognise that there is a primary key. Please see the logs of the application:- **** Fri Feb 4 11:19:58 2011 [ERROR]: can't support updateable resultset for table public.FILEDOCUMENTS, because resultset does not contain a part of the primary key ( column FILEDOCUMENTID is missing ) Fri Feb 4 11:19:58 2011 [SQL]: executed query 'SELECT "FILESTEPSID", "Filename", "Description","FileDate","FileFeeEarner","UnitsOfTime","BillingCategory","IsOpenOffice?", "FILEDOCUMENTID" FROM "FILEDOCUMENTS" WHERE "FILEDOCUMENTID"=1072' sucessfully, duration=1ms, returnedRows=1. **** Look at the error message, and then the next line - which actually contains the "select" statement - the last column selected before the 'WHERE' is the primary key column. The JDBC driver does not have this problem, but I would prefer not to use it as it runs around 50 - 75% slower on my 32 bit machines, and around 500% slower on 64bit machine! Thanks. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
