Dropping a table referenced in a view

Hi, I see that in derby if a table is being referenced in a view, we need to drop the view first and then only we can drop the table being referenced in a view. But in DB2, we do allow users to drop the table and we mark the view invalid. So just wondering why we don't the same in Derby and are

[jira] Created: (DERBY-3145) ComparisonFailure in synonym(org.apache.derbyTesting.functionTests.tests.lang.LangScripts)

ComparisonFailure in synonym(org.apache.derbyTesting.functionTests.tests.lang.LangScripts) -- Key: DERBY-3145 URL: https://issues.apache.org/jira/browse/DERBY-3145

[jira] Commented: (DERBY-2914) new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS, SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented

[ https://issues.apache.org/jira/browse/DERBY-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537232 ] John H. Embretsen commented on DERBY-2914: -- Trunk commit looks OK - related parts of the (alpha) ref guide

[jira] Updated: (DERBY-3133) Syntax for GRANT table permission does not mention that several privileges may be specified in a list

[ https://issues.apache.org/jira/browse/DERBY-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-3133: - Attachment: rrefsqljrevoke-2.html rrefsqljgrant-2.html Thanks, Laura! I adjusted

[jira] Commented: (DERBY-2212) Add Unique where not null to create index

[ https://issues.apache.org/jira/browse/DERBY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537281 ] Anurag Shekhar commented on DERBY-2212: --- thanks Mike for the comments. I will update the functional spec and

Compilation problem - head of trunk and JDK6

In the current proof of concept replication code, we boot the slave database by calling Database db = (Database)Monitor.findService(Property.DATABASE_MODULE, dbname); This requires org.apache.derby.iapi.db.Database to be imported. With the head of trunk, this import results in compilation

Re: Compilation problem - head of trunk and JDK6

I get the same errors. My changes in NetworkServerControlImpl.java imports are: added import org.apache.derby.iapi.services.mbeans.ManagementService; import javax.management.ObjectName; removed: import org.apache.derby.iapi.services.info.JVMInfo; AND I switched to Netbeans 6.0beta2 and

Re: Compilation problem - head of trunk and JDK6

Jørgen Løland wrote: In the current proof of concept replication code, we boot the slave database by calling Database db = (Database)Monitor.findService(Property.DATABASE_MODULE, dbname); This requires org.apache.derby.iapi.db.Database to be imported. With the head of trunk, this import

Re: Compilation problem - head of trunk and JDK6

Oystein Grovlen - Sun Norway wrote: I get this error without any changes to NetworkServerControlImpl. (My only changes are some local changes in LogToFile). I think the problem is that VTI demo does not implement Blob methods that are new to JDBC 4. I guess either the build system should

Re: JUnit memory consumption

Kathey Marsden wrote: Upon more research it seems that JUnit creates one instance of each test class per fixture and keeps that reference until the end of the suites.All run. That means any state in the test hangs around as well, which slowly adds up as the test runs. This is particularly

Re: Compilation problem - head of trunk and JDK6

I think the reason is that the VTI demo result set template presumes JDK1.5, since the JDBC has more methods in JDK 1.6 which are unimplemented in the VTI template. Dag

[jira] Created: (DERBY-3146) Adjust length restriction on user identifiers (authorization ids) to same as other identifiers

Adjust length restriction on user identifiers (authorization ids) to same as other identifiers -- Key: DERBY-3146 URL: https://issues.apache.org/jira/browse/DERBY-3146

Re: Compilation problem - head of trunk and JDK6

Oystein Grovlen - Sun Norway wrote: Jørgen Løland wrote: In the current proof of concept replication code, we boot the slave database by calling Database db = (Database)Monitor.findService(Property.DATABASE_MODULE, dbname); This requires org.apache.derby.iapi.db.Database to be imported.

[jira] Updated: (DERBY-3129) Create Demo code, showing how to create and use table functions.

[ https://issues.apache.org/jira/browse/DERBY-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3129: - Attachment: derby-3129-02-buildfix-aa.diff Committed derby-3129-02-buildfix-aa.diff. This is

Re: Compilation problem - head of trunk and JDK6

Dag H. Wanvik wrote: I think the reason is that the VTI demo result set template presumes JDK1.5, since the JDBC has more methods in JDK 1.6 which are unimplemented in the VTI template. Dag I just checked in submission 587905. Hopefully this fixes the build in Java 6 environments. Please

[jira] Subscription: Derby: JIRA issues with patch available

Issue Subscription Filter: Derby: JIRA issues with patch available (21 issues) Subscriber: derby-dev Key Summary DERBY-3133 Syntax for GRANT table permission does not mention that several privileges may be specified in a list https://issues.apache.org/jira/browse/DERBY-3133

Regression Test Report - Daily 587546 - Sun DBTG

[Auto-generated mail] *Daily* 587546/2007-10-23 18:00:32 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0288288 073.32% derbyall 097139713 0 1203.54% suitesAll sles 0

[jira] Commented: (DERBY-3146) Adjust length restriction on user identifiers (authorization ids) to same as other identifiers

[ https://issues.apache.org/jira/browse/DERBY-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537353 ] Bryan Pendleton commented on DERBY-3146: This seems like a good idea to me, thanks for logging it! Are

Re: Dropping a table referenced in a view

I see that in derby if a table is being referenced in a view, we need to drop the view first and then only we can drop the table being referenced in a view. But in DB2, we do allow users to drop the table and we mark the view invalid. So just wondering why we don't the same in Derby and are

[jira] Updated: (DERBY-2188) Developer's Guide talks about a jdbc url property locale which is not supported by Derby.

[ https://issues.apache.org/jira/browse/DERBY-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laura Stewart updated DERBY-2188: - Attachment: rtoolsijpropref97949.html derby2188_2.diff Thanks for catching this

[jira] Assigned: (DERBY-3145) ComparisonFailure in synonym(org.apache.derbyTesting.functionTests.tests.lang.LangScripts)

[ https://issues.apache.org/jira/browse/DERBY-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor reassigned DERBY-3145: -- Assignee: Mamta A. Satoor ComparisonFailure in

[jira] Commented: (DERBY-2017) Client driver can insert and commit partial data when a LOB stream throws IOException or does not match the specified length

[ https://issues.apache.org/jira/browse/DERBY-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537365 ] Kathey Marsden commented on DERBY-2017: --- Mayuresh, are you actively working on this issue? Client driver

[jira] Assigned: (DERBY-3110) server hangs after trace on command fails

[ https://issues.apache.org/jira/browse/DERBY-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden reassigned DERBY-3110: - Assignee: Kathey Marsden server hangs after trace on command fails

[jira] Commented: (DERBY-2914) new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS, SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented

[ https://issues.apache.org/jira/browse/DERBY-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537366 ] Laura Stewart commented on DERBY-2914: -- Hi John - I'll change the nav title in another issue. The topicref

[jira] Commented: (DERBY-3133) Syntax for GRANT table permission does not mention that several privileges may be specified in a list

[ https://issues.apache.org/jira/browse/DERBY-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537369 ] Laura Stewart commented on DERBY-3133: -- Dag - Your changes look good, much cleaner. You updated only the html

[jira] Assigned: (DERBY-3088) convert to junit, or otherwise eliminate version in tests which require an update of the master in the release management process

[ https://issues.apache.org/jira/browse/DERBY-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrna van Lunteren reassigned DERBY-3088: - Assignee: Myrna van Lunteren convert to junit, or otherwise eliminate version

[jira] Commented: (DERBY-3088) convert to junit, or otherwise eliminate version in tests which require an update of the master in the release management process

[ https://issues.apache.org/jira/browse/DERBY-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537375 ] Myrna van Lunteren commented on DERBY-3088: --- removed metadata* from the list by commenting out the driver

Regression Test Report - tinderbox_trunk16 587905 - Sun DBTG

[Auto-generated mail] *tinderbox_trunk16* 587905/2007-10-24 17:12:19 CEST Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* SunOS-5.10_i86pc-i386 0288288 088.00% derbyall F:1,E:097149713 0

[jira] Updated: (DERBY-1823) Derby Developer's Guide - Issues w/ User authentication and authorization extended examples section/paragraph

[ https://issues.apache.org/jira/browse/DERBY-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Haase updated DERBY-1823: - Attachment: DERBY-1823-3.zip DERBY-1823-4.diff Attaching DERBY-1823-4.diff and

[jira] Updated: (DERBY-3117) Adjust master build script to require the Java 5 compiler to build Derby

[ https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3117: - Attachment: BuildDefaults.txt I have attached a proposal for how the build scripts could

[jira] Resolved: (DERBY-3145) ComparisonFailure in synonym(org.apache.derbyTesting.functionTests.tests.lang.LangScripts)

[ https://issues.apache.org/jira/browse/DERBY-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor resolved DERBY-3145. Resolution: Fixed Fix Version/s: 10.4.0.0 10.3.1.5 Migrated

[jira] Closed: (DERBY-3145) ComparisonFailure in synonym(org.apache.derbyTesting.functionTests.tests.lang.LangScripts)

[ https://issues.apache.org/jira/browse/DERBY-3145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor closed DERBY-3145. -- ComparisonFailure in synonym(org.apache.derbyTesting.functionTests.tests.lang.LangScripts)

[jira] Commented: (DERBY-2905) Shutting down embedded Derby does not remove all code, the AutoloadDriver is left registered in the DriverManager.

[ https://issues.apache.org/jira/browse/DERBY-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537404 ] Daniel John Debrunner commented on DERBY-2905: -- I think the patch results in code that is brittle, it

[jira] Created: (DERBY-3147) Remove unused code that allow identifiers to be lower-cased.

Remove unused code that allow identifiers to be lower-cased. Key: DERBY-3147 URL: https://issues.apache.org/jira/browse/DERBY-3147 Project: Derby Issue Type: Improvement

[jira] Commented: (DERBY-70) Incorrect documentation about class loading from installed jar files.

[ https://issues.apache.org/jira/browse/DERBY-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537414 ] Daniel John Debrunner commented on DERBY-70: The section still seems a little unclear to me. Instead of

[jira] Commented: (DERBY-3117) Adjust master build script to require the Java 5 compiler to build Derby

[ https://issues.apache.org/jira/browse/DERBY-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537415 ] Daniel John Debrunner commented on DERBY-3117: -- The compiler check is invoked when running the tests

[jira] Created: (DERBY-3148) IllegalArgumentException: Malformed \uxxxx encoding while trying to find Xalan version running tests via ant

IllegalArgumentException: Malformed \u encoding while trying to find Xalan version running tests via ant Key: DERBY-3148 URL:

[jira] Commented: (DERBY-3148) IllegalArgumentException: Malformed \uxxxx encoding while trying to find Xalan version running tests via ant

[ https://issues.apache.org/jira/browse/DERBY-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537428 ] Daniel John Debrunner commented on DERBY-3148: -- The issue is that

[jira] Assigned: (DERBY-3148) IllegalArgumentException: Malformed \uxxxx encoding while trying to find Xalan version running tests via ant

[ https://issues.apache.org/jira/browse/DERBY-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel John Debrunner reassigned DERBY-3148: Assignee: (was: Daniel John Debrunner) IllegalArgumentException:

security exceptions when running the junit tests via the ant harness

I am seeing security exceptions when I run the junit tests via the ant harness. Since I don't normally run the junit tests that way, I'm guessing this is an environment problem. Does the following kind of error look familiar to anyone? Thanks-Rick [junit] Running

[jira] Updated: (DERBY-3148) IllegalArgumentException: Malformed \uxxxx encoding while trying to find Xalan version running tests via ant

[ https://issues.apache.org/jira/browse/DERBY-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-3148: --- Attachment: d3148_v1.patch Attaching a simple patch which moves away from parsing the EnvironmentCheck output as

[jira] Commented: (DERBY-3148) IllegalArgumentException: Malformed \uxxxx encoding while trying to find Xalan version running tests via ant

[ https://issues.apache.org/jira/browse/DERBY-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537453 ] A B commented on DERBY-3148: Actually, I guess it is too naive. If the string version.xalan2_2 shows up in the

[jira] Commented: (DERBY-2245) DatabaseMetaData.getSQLKeywords() contains words that are not keywords in Derby.

[ https://issues.apache.org/jira/browse/DERBY-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537460 ] Myrna van Lunteren commented on DERBY-2245: --- Is this issue stalled? Revision 504234 only removed REFRESH

[jira] Commented: (DERBY-2245) DatabaseMetaData.getSQLKeywords() contains words that are not keywords in Derby.

[ https://issues.apache.org/jira/browse/DERBY-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537469 ] Daniel John Debrunner commented on DERBY-2245: -- Does a keyword being reserved has anything to do with

[jira] Commented: (DERBY-3148) IllegalArgumentException: Malformed \uxxxx encoding while trying to find Xalan version running tests via ant

[ https://issues.apache.org/jira/browse/DERBY-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537471 ] Daniel John Debrunner commented on DERBY-3148: -- With the patch the byte array is written using the

[jira] Commented: (DERBY-3148) IllegalArgumentException: Malformed \uxxxx encoding while trying to find Xalan version running tests via ant

[ https://issues.apache.org/jira/browse/DERBY-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537472 ] Daniel John Debrunner commented on DERBY-3148: -- maybe checking for indexOf(version.xalan2_2=) [note the

[jira] Commented: (DERBY-2242) Convert jdbcapi/metadata.java to JUnit test.

[ https://issues.apache.org/jira/browse/DERBY-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537478 ] Myrna van Lunteren commented on DERBY-2242: --- I started looking at the getSQLKeywords //TODO, thinking we

Re: [jira] Commented: (DERBY-2245) DatabaseMetaData.getSQLKeywords() contains words that are not keywords in Derby.

On 10/24/07, Daniel John Debrunner (JIRA) [EMAIL PROTECTED] wrote: [ https://issues.apache.org/jira/browse/DERBY-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537469 ] Daniel John Debrunner commented on DERBY-2245:

[jira] Commented: (DERBY-3136) Cut down on object creations in LIKE clause implementation of territory based characters.

[ https://issues.apache.org/jira/browse/DERBY-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537498 ] Mamta A. Satoor commented on DERBY-3136: I incorporated the changes suggested by Knut into trunk using

Re: Compilation problem - head of trunk and JDK6

Rick Hillegas wrote: Dag H. Wanvik wrote: I think the reason is that the VTI demo result set template presumes JDK1.5, since the JDBC has more methods in JDK 1.6 which are unimplemented in the VTI template. Dag I just checked in submission 587905. Hopefully this fixes the build in Java 6

[jira] Closed: (DERBY-3136) Cut down on object creations in LIKE clause implementation of territory based characters.

[ https://issues.apache.org/jira/browse/DERBY-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor closed DERBY-3136. -- Cut down on object creations in LIKE clause implementation of territory based characters.

[jira] Resolved: (DERBY-3136) Cut down on object creations in LIKE clause implementation of territory based characters.

[ https://issues.apache.org/jira/browse/DERBY-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor resolved DERBY-3136. Resolution: Fixed Fix Version/s: 10.4.0.0 10.3.1.5 Merged

[jira] Commented: (DERBY-3139) setObject and other setXXX methods on PreparedStatement throw different exceptions in Network Server when parameter number is out of range

[ https://issues.apache.org/jira/browse/DERBY-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537503 ] Mamta A. Satoor commented on DERBY-3139: I will work on this tomorrow ie change the SQL State for network

[jira] Assigned: (DERBY-3139) setObject and other setXXX methods on PreparedStatement throw different exceptions in Network Server when parameter number is out of range

[ https://issues.apache.org/jira/browse/DERBY-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor reassigned DERBY-3139: -- Assignee: Mamta A. Satoor setObject and other setXXX methods on PreparedStatement