Issue 44200 - HSQLDB Tables names aren't case sensitive, tables names in SQL are case sensitive
Summary: HSQLDB Tables names aren't case sensitive, tables names in SQL are case sensi...
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0 Beta
Hardware: All Linux, all
: P3 Trivial with 1 vote (vote)
Target Milestone: OOo 2.1
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords: needmoreinfo, oooqa, regression
: 52997 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-03-06 00:08 UTC by xevivi
Modified: 2006-10-20 13:03 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description xevivi 2005-03-06 00:08:59 UTC 
Hi,

I'm using the database application and I find something curious.

I can't create two tables with the same name, one in upper case and the other
with lower case. Ok, for this reason I thougth tables names aren't case
sensitive. (like oracle, postgresql, mysql ...)

But when I create querys in SQL View, the tables names are case sensitive. 

For this reason, if I create a table named TABLE, the following query fails:

SELECT * FROM table;

In my opinnion, this shouldn't be the normal behavior and it should be treated
like a bug.

Regards,

Xevi.
Comment 1 flibby05 2005-03-24 19:28:29 UTC 
Hello xevivi,
are you creating the tables in a hsqldb or in another database (f.e. mysql)?
Max
Comment 2 xevivi 2005-03-24 20:18:23 UTC 
Hello Max,

I create the tables in hsqldb, using the default OpenOffice.org installation.

Regards,

Xevi.
Comment 3 flibby05 2005-04-03 11:28:45 UTC 
will check the spec
Comment 4 flibby05 2005-04-05 21:03:32 UTC 
checked table_wizard.sxw, found nothing useful.

confirm behaviour.

marc, can you decide on this issue?
Comment 5 flibby05 2005-04-21 13:47:42 UTC 
should be fixed with issue 41785
Comment 6 marc.neumann 2005-04-22 10:59:20 UTC 
first set the target to "Office Later"

second I send it to the right developer.

msc -> oj: I can reproduce this with hsqldb. Can we change  anything in this
behaviour?
Comment 7 marc.neumann 2005-04-22 11:00:01 UTC 
reassign
Comment 8 ocke.janssen 2006-01-02 08:00:36 UTC 
*** Issue 52997 has been marked as a duplicate of this issue. ***
Comment 9 ocke.janssen 2006-01-02 10:02:02 UTC 
Fixed in cws dba30
Comment 10 Frank Schönheit 2006-05-11 14:03:27 UTC 
fs-> msc: please verify in CWS dba30

re-open issue and reassign to msc
Comment 11 Frank Schönheit 2006-05-11 14:03:32 UTC 
reassign to msc
Comment 12 Frank Schönheit 2006-05-11 14:03:40 UTC 
reset resolution to FIXED
Comment 13 Frank Schönheit 2006-05-12 07:34:49 UTC 
targeting to 2.0.4, as the fix is already available, and has meanwhile been
checked in in a 2.0.4-CWS
Comment 14 Frank Schönheit 2006-05-12 07:38:35 UTC 
this used to work in some recent build -> keyword "regression"
Comment 15 Frank Schönheit 2006-05-12 07:39:58 UTC 
targeting to 2.0.4, as the fix is already available, and has meanwhile been
checked in in a 2.0.4-CWS
Comment 16 marc.neumann 2006-05-18 11:19:04 UTC 
verified in CWS dba30

find more information about this CWS, like when it is available in the master
builds, in EIS, the Environment Information System:
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=SRC680%2Fdba30
Comment 17 Frank Schönheit 2006-08-11 11:21:05 UTC 
targeting to 2.1, since the fix is part of a CWS aiming for this release
Comment 18 marc.neumann 2006-10-20 13:03:11 UTC 
Hi,

this is fixed in the current master. The current master is available at
http://download.openoffice.org/680/index.html

I close this issue now.

Bye Marc