db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Dudziak (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DDLUTILS-55) HsqlDb PlatformInfo should not use delimited identifiers
Date Tue, 20 Dec 2005 08:07:31 GMT
     [ http://issues.apache.org/jira/browse/DDLUTILS-55?page=all ]
Thomas Dudziak resolved DDLUTILS-55:

    Resolution: Invalid

There are two modes in which (most) databases can operate. In the first one where undelimited
identifiers are used, all table/column/... identifiers are converted to uppercase and they
have to follow certain rules (no whitespaces, no SQL keywords etc.). In the second way, where
these identifiers are surrounded by delimiters, the database treats them as is. Here the identifiers
can be anything, even SQL keywords.
DdlUtils per default is in this second mode, so that the identifiers are in the database as
they are in the code that created the database. You can switch the mode via the PlatformInfo
as you've already noticed.

> HsqlDb PlatformInfo should not use delimited identifiers
> --------------------------------------------------------
>          Key: DDLUTILS-55
>          URL: http://issues.apache.org/jira/browse/DDLUTILS-55
>      Project: DdlUtils
>         Type: Bug
>     Reporter: Ken Weiner
>     Assignee: Thomas Dudziak
>  Attachments: HsqlDbPlatform-patch.txt
> Currently, when creating tables using HSQLDB, double quotes (") are used surrounding
the table names in each CREATE TABLE statement.  For example,
> CREATE TABLE "person" ...
> As a result, it isn't possible to write SQL without putting double quotes around tables
names.  For example, this statement doesn't work:
> select * from person;
> But this one does:
> select * from "person";
> If useDelimitedIdentifiers in PlatformInfo is set to false, then double quotes will not
surround the table names in CREATE TABLE statements and then SQL statements will work as expected
(without having to include the double quotes).
> I will attach a patch for this simple change.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message