db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4842) Support "IF [NOT] EXISTS" in CREATE TABLE and "IF EXISTS" in DROP TABLE
Date Wed, 13 Oct 2010 12:54:33 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920521#action_12920521
] 

Rick Hillegas commented on DERBY-4842:
--------------------------------------

Thanks for the suggestion, Adrian. The MySQL 6.0 syntax for declaring a table is this:

CREATE TABLE [IF NOT EXISTS] tableName ...

and the MySQL syntax for removing a table is this:

DROP TABLE [IF EXISTS] tableName ...

These clauses are MySQL extensions which are not part of the ANSI/ISO SQL Standard. This functionality
may be peculiar to MySQL: I can't find anything similar documented for Postgres, Oracle, or
DB2.

> Support "IF [NOT] EXISTS" in CREATE TABLE and "IF  EXISTS" in DROP TABLE 
> -------------------------------------------------------------------------
>
>                 Key: DERBY-4842
>                 URL: https://issues.apache.org/jira/browse/DERBY-4842
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Adrian Tarau
>
> It would be really great if Derby will support these additions similar with what MySQL
has.
> Also a way to disable constraints when dropping the whole database, so you would not
be forced to put DROPs in such an order that constraints will not fail. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message