Apache OpenOffice (AOO) Bugzilla – Issue 21300
Quoting in (JDBC generated)SQL does not work in Sybase (#20536 part 1)
Last modified: 2013-08-07 15:45:41 UTC
I'm trying RC5 against a Sybase 12.5 release on Linux (a production database). OOo seems to be configured to quote all parts of a statement; select "firstkey" from "jaap"."dbo"."first" "first" This produces the error: "jaap"."dbo"."first" not found. specify owner.objectname or use sp_help[....]. If I force (default the view gets quoted) a view on jaap.dbo.first, the table is accessible. This behaviour seems to be consistent; I tried opening tables, writing views, creating forms.. This behaviour makes OOo unuseable with Sybase. I can't find away to configure this behaviour so : Is it configurable? If not I think this is a defect or at least a needed enhancement. Jaap Bril
Hi Ocke, As far as I know it's OK to quote all schema, catalog table on a datasource . f.e. with a ms sql server database this works. I can't reproduce it with a sybase database because my database has only a schema and the table name (no catalog). Is there anything we can do to fix this? May be provide a new setting for a datasource or something else. If not I would say we close this issue as invalid. Bye Marc
I put the issue to Sybase; The quoting as done by OOo has never been seen by my contact; but he will ask around. BTW The problem occurs in the SQL-parser so (as Sybase reads them) this way of quoting is outside the SQL-specs. I would like to be sure one way or the other. Which (version of the) specs are being used? Jaap
*** Issue 12742 has been marked as a duplicate of this issue. ***
change subcomponent to 'none'
Hi Jaap, would it be okay for you, when the user is allowed to turn off the use of the catalog name and/or the schema name too. So in that case only the parts which are not turned off will be quoted? You may have a look at the spec for the new database property dialog http://dba.openoffice.org/specifications/Data_Source_Property_Dialog.sxw Best regards, Ocke PS: If the answer is "yes", you may close this issue.
Set to fixed and closing this issue.
.