You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2012/09/28 19:19:07 UTC

[jira] [Commented] (DERBY-4842) Support "IF [NOT] EXISTS" in CREATE TABLE and "IF EXISTS" in DROP TABLE

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

Mamta A. Satoor commented on DERBY-4842:
----------------------------------------

I was wondering if we can close this issue since the SQL enhancement requested is not part of ANSI/ISO SQL Standard. 

As for drop schema cascade, there is DERBY-4029(DERBY-4844 has been closed as a duplicate of DERBY-4029). I will link this issue to DERBY-4029.
                
> 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
>              Labels: derby_triage10_10
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira