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 de...@db.apache.org on 2004/10/11 06:47:51 UTC
[jira] Created: (DERBY-38) Make LOCKS as non-reserved keyword in Derby since it is not a reserved keyword in the SQL standards
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DERBY-38
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DERBY-38
Summary: Make LOCKS as non-reserved keyword in Derby since it is not a reserved keyword in the SQL standards
Type: Bug
Status: Unassigned
Priority: Major
Project: Derby
Components:
SQL
Versions:
10.0.2.0
Assignee:
Reporter: Mamta A. Satoor
Created: Sun, 10 Oct 2004 9:47 PM
Updated: Sun, 10 Oct 2004 9:47 PM
Environment: For all the platforms
Description:
Since LOCKS is not a reserved keyword in SQL standards, Derby should not make LOCKS as reserved keyword.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-38) Make LOCKS as non-reserved keyword in Derby since it is not a reserved keyword in the SQL standards
Posted by de...@db.apache.org.
Message:
The following issue has been closed.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DERBY-38
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DERBY-38
Summary: Make LOCKS as non-reserved keyword in Derby since it is not a reserved keyword in the SQL standards
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Derby
Components:
SQL
Fix Fors:
10.0.2.0
Versions:
10.0.2.0
Assignee: Mamta A. Satoor
Reporter: Mamta A. Satoor
Created: Sun, 10 Oct 2004 9:47 PM
Updated: Wed, 13 Oct 2004 7:53 AM
Environment: For all the platforms
Description:
Since LOCKS is not a reserved keyword in SQL standards, Derby should not make LOCKS as reserved keyword.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-38) Make LOCKS as non-reserved keyword in Derby since it is not a reserved keyword in the SQL standards
Posted by de...@db.apache.org.
The following issue has been updated:
Updater: Mamta A. Satoor (mailto:mamta@Remulak.Net)
Date: Wed, 13 Oct 2004 7:52 AM
Changes:
assignee changed to Mamta A. Satoor
Fix Version changed to 10.0.2.0
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/DERBY-38?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/DERBY-38
Here is an overview of the issue:
---------------------------------------------------------------------
Key: DERBY-38
Summary: Make LOCKS as non-reserved keyword in Derby since it is not a reserved keyword in the SQL standards
Type: Bug
Status: Open
Priority: Major
Project: Derby
Components:
SQL
Fix Fors:
10.0.2.0
Versions:
10.0.2.0
Assignee: Mamta A. Satoor
Reporter: Mamta A. Satoor
Created: Sun, 10 Oct 2004 9:47 PM
Updated: Wed, 13 Oct 2004 7:52 AM
Environment: For all the platforms
Description:
Since LOCKS is not a reserved keyword in SQL standards, Derby should not make LOCKS as reserved keyword.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira