Apache OpenOffice (AOO) Bugzilla – Issue 63221
copy table from calc to db2/400 db tables does not work as expected
Last modified: 2013-08-07 15:45:17 UTC
I've dragged data from calc to a table in an database connected via ODBC to a DB2/400 UDB. The creation came back with an error telling me, that the HLITSTRBU would not be identical to the server. For the name of the table I've entered HLITSTRBU.OOIMP2 which is a valid combination for naming within DB2/400. I wanted to create table ooimp2 in hlitstrbu schema. You generated: CREATE TABLE "HLITSTRBU"."ES_BUND"."IMPOO2" ("DIVSA" VARGRAPHIC(255) CCSID 13488,"DIVSF" VARGRAPHIC(255) CCSID 13488,"DISPRC" VARGRAPHIC(255) CCSID 13488,"DIVRKY" VARGRAPHIC(255) CCSID 13488,"DIF1" VARGRAPHIC(255) CCSID 13488,"DIKEY2" VARGRAPHIC(255) CCSID 13488,"DIVDAT" VARGRAPHIC(255) CCSID 13488,"DIF2" VARGRAPHIC(255) CCSID 13488,"DIVAKZ" VARGRAPHIC(255) CCSID 13488,"DIVSKZ" VARGRAPHIC(255) CCSID 13488,"DIDTAD" VARGRAPHIC(255) CCSID 13488,"DIDTUP" VARGRAPHIC(255) CCSID 13488,"DIUSUP" VARGRAPHIC(255) CCSID 13488,"DIIACS" VARGRAPHIC(255) CCSID 13488) correctly it should be: CREATE TABLE "HLITSTRBU"."IMPOO2" ("DIVSA" VARGRAPHIC(255) CCSID 13488,"DIVSF" VARGRAPHIC(255) CCSID 13488,"DISPRC" VARGRAPHIC(255) CCSID 13488,"DIVRKY" VARGRAPHIC(255) CCSID 13488,"DIF1" VARGRAPHIC(255) CCSID 13488,"DIKEY2" VARGRAPHIC(255) CCSID 13488,"DIVDAT" VARGRAPHIC(255) CCSID 13488,"DIF2" VARGRAPHIC(255) CCSID 13488,"DIVAKZ" VARGRAPHIC(255) CCSID 13488,"DIVSKZ" VARGRAPHIC(255) CCSID 13488,"DIDTAD" VARGRAPHIC(255) CCSID 13488,"DIDTUP" VARGRAPHIC(255) CCSID 13488,"DIUSUP" VARGRAPHIC(255) CCSID 13488,"DIIACS" VARGRAPHIC(255) CCSID 13488) In addition please be aware, that quoting names means, that there must exists a perfect match between the case names are entered and the names as stored in the DB. DB2, as most other DB Servers, normaly have names unquoted and converts them to capital letters. Only when names are quoted the system does an exact match. Therefore it could cause problems to quote.
change owner
clu->rabund: sorry, this case is similar to issue #63222 - this is the way oo quotes and it works fine for a lot of databases - feel free to write a feature enhancement to change that behavior, but it is no bug (such discussions like if the quoting is proper or not is welcome in the corresponding newsgroups or oo mailinglists) thx
clu->rabund: 'workaround': if you want to use other quoting, you have also the possibility to run your sql commands directly (menue: tools/sql or in query design to switch off the design mode and run sql command directly) hope that helps
Hi, it's not a feature request. It is definitely a bug. Even when entering the SQL statement directly OO changes it. This "feature" of OO makes the database part of the suite useless. What I don't understand is, that all theses problem have been solved in the past (SO 5.2, 6). Only with the new DB module all the bugs are back again. By the way, you will see the same problem not only for DB2/400 UDB but also for Mimer and I think for most of the other databases not coming from the open source community. Regards, Ralf
clu->rabund: sorry for closing this issue, i have mistaken it with the 'quoting' problem - i will investigate that further p.s. thank you for your patience
clu->all: i cannot repro that problem on a DB2 Universal Database Vers.7.2 over ODBC (d&ding works fine for me, also 'HLITSTRBU.OOIMP2' as tablename etc.) - i do not no the difference to the mentioned DB2/400, but there seems to be one - in view that i do not have the possibility to test on such a server, maybe someone else can confirm that problem thx
fit summary
added keyword: 'needhelp'
How can I assist you?
clu->rabund: 1.) if you have a hint how i can repro your problem with my stuff would help 2.) if an other person with similar problem on equal system could acknowledge this problem would also help => a main rule on oo is that an issue has to be reproducable and in cases with properitary software this can get difficult
Hi Clu, I've did some testing with OO 2.0.3 and there is still the same problem. When you've connected to an DB2400/UDB you just address tables by schema.table. When you enter the filename like this, OO converts it to schema.database.table witch is wrong. Correctly it should be database.schema.table. When you enter the table name like this when creating it OO works fine (as long as you enter the name completely in capital letters, you remember the problem of the '"'?). You just can test this beheaviour when you've got an AS/400; iSeries; i5 to test. At the moment I don't have another type of DB system available to test the behaviour. regards, Ralf
clu->fs: we have no possibility to test that, because of the properitary software, and i do not think this will be confirmend by an other user in senseful time, so maybe you can have a look at that problem in a quiet minute from developer side thx
Hi, how about giving a way to configure the behaviour of OO? At the connection setting could be an option whether OO is allowed to add '"' and change the access path of a databaseobject in a sql statement. Default behaviour could be the same as it is now and the user can decide if other settings would work better for him. Regards, Ralf
This Issue requires more information ('needmoreinfo'), but has not been updated within the last year. Please re-test with one of the latest versions of OOo - the problem(s) may have already been addressed. Either use the recent stable version: http://download.openoffice.org/index.html or consider trying the new OOo 3 BETA (still in testing): http://download.openoffice.org/3.0beta/ Please report back the outcome so this Issue may be closed or progressed as necessary - otherwise it may be Resolved as Invalid in the future. You may also wish to search for (and note) any duplicates of this Issue that may have advanced further : http://www.openoffice.org/issues/query.cgi Regards, Andrew Cleaning-up and Closing old Issues as part of: ~ The Grand Bug Squash, pre v3 ~
Hi, I've just checked the behaviour of 3.0.0 Beta. When You enter the schema and table like SCHEMA.TABLE, OO adds the Systemname it results in the following "SCHEMA"."SYSTEM"."TABLE" which is wrong. It has to be "SYSTEM"."SCHEMA"."TABLE". When you enter schema and table like "schema"."table" OO generates ""schema""."SYSTEM".""table"" which is completely rubbish. It has to be "SYSTEM"."schema"."table". Double-double quotes are not allowed in any way. Anyway when you're entering SYSTEM.SCHEMA.TABLE OO generates a valid Statement and copying ist working fine. Kindest Ralf
@ sinonaw Can you have a look?
no chance to reproduce it => wont fixed at this time
-< closed