[jira] Created: (DERBY-3188) 'Failure in loading T2 native library db2jcct2' in lang/triggerGeneral.sql

'Failure in loading T2 native library db2jcct2' in lang/triggerGeneral.sql -- Key: DERBY-3188 URL: https://issues.apache.org/jira/browse/DERBY-3188 Project: Derby Issue

Re: TriggerGeneral test failure

Bryan Pendleton wrote: I'm seeing this failure in my regression runs, with the current trunk. Can anybody shed some light on what this failure is trying to tell me? Do I have a configuration problem of some sort, or is this perhaps due to a change I've made? * Diff file derbyall/derbyla

[jira] Commented: (DERBY-3177) Dropping columns casues auto_increment field to be lost

[ https://issues.apache.org/jira/browse/DERBY-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540962 ] Bryan Pendleton commented on DERBY-3177: Unfortunately, I can't think of an easy way to repair the SYSCOLUMNS

[jira] Commented: (DERBY-3175) NullPointerException on INSERT after ALTER TABLE ... DROP COLUMN

[ https://issues.apache.org/jira/browse/DERBY-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540963 ] Bryan Pendleton commented on DERBY-3175: Except for a strange failure in lang/triggerGeneral, all the regress

[jira] Updated: (DERBY-3175) NullPointerException on INSERT after ALTER TABLE ... DROP COLUMN

[ https://issues.apache.org/jira/browse/DERBY-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-3175: --- Derby Info: [Patch Available] > NullPointerException on INSERT after ALTER TABLE ... DROP COL

[jira] Updated: (DERBY-3175) NullPointerException on INSERT after ALTER TABLE ... DROP COLUMN

[ https://issues.apache.org/jira/browse/DERBY-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-3175: --- Attachment: fixWith3177Case.diff Attached is "fixWith3177Case.diff", a patch proposal. I bel

TriggerGeneral test failure

I'm seeing this failure in my regression runs, with the current trunk. Can anybody shed some light on what this failure is trying to tell me? Do I have a configuration problem of some sort, or is this perhaps due to a change I've made? * Diff file derbyall/derbylang/triggerGeneral.diff *

Re: [jira] Created: (DERBY-3185) SET (TRANSACTION) ISOLATION (LEVEL) is not SQL compliant

"Dyre Tjeldvoll (JIRA)" <[EMAIL PROTECTED]> writes: > An alternative is to add a new SQL compliant SET TRANSACTION which > uses the standard isolation level specifiers, and keep SET (CURRENT) > ISOLATION as it is today for backward compatibility. This is in deed confusing. Derby currently uses th

[jira] Updated: (DERBY-3137) SQL roles: add catalog support

[ https://issues.apache.org/jira/browse/DERBY-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-3137: - Derby Info: [Patch Available] > SQL roles: add catalog support > -- >

[jira] Updated: (DERBY-3137) SQL roles: add catalog support

[ https://issues.apache.org/jira/browse/DERBY-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-3137: - Attachment: DERBY-3137-2.stat DERBY-3137-2.diff Upload a new version of the first

[jira] Commented: (DERBY-3172) ConnectionEventListener.connectionErrorOccurred not being executed when SQLState 08006 Error is thrown

[ https://issues.apache.org/jira/browse/DERBY-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540934 ] Mamta A. Satoor commented on DERBY-3172: Thanks, Manjula. I will look at it for embedded test case. > Connec

[jira] Commented: (DERBY-3172) ConnectionEventListener.connectionErrorOccurred not being executed when SQLState 08006 Error is thrown

[ https://issues.apache.org/jira/browse/DERBY-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540925 ] Manjula Kutty commented on DERBY-3172: -- There is this test called ShutdownDatabaseTest.java in lang which does t

[jira] Updated: (DERBY-3176) J2ME support for phoneME platform disabled in 10.3

[ https://issues.apache.org/jira/browse/DERBY-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3176: - Attachment: derby-3176-01-phoneME-ad.diff Thanks for the continued advice, Dan. I am attaching d

Re: Installing a SecurityManager by default when the server boots

IMHO, if we are breaking a lot of existing applications, then it was not a compatible change, and needs to be turned off. I understand the value of "secure by default' but I think this has to be balanced against the value of Derby as a very quickly easy to use and run database which makes it a fav

Re: Confustion about locale and error messages

Is there anyone that explain how locale works with Derby error messages? On 10/29/07, Laura Stewart <[EMAIL PROTECTED]> wrote: > Hi - Derby-2188 is about locale info within Derby. One file, > cdevin55108.html, has some confusing info about locale and error > messages. > > Below is from Mamta's co

[jira] Commented: (DERBY-3172) ConnectionEventListener.connectionErrorOccurred not being executed when SQLState 08006 Error is thrown

[ https://issues.apache.org/jira/browse/DERBY-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540896 ] Mamta A. Satoor commented on DERBY-3172: I was thinking about junit testing for the proposed fix and having 2

[jira] Commented: (DERBY-3052) testStalePlanCheckIntervalOutOfRange(org.apache.derbyTesting.functionTests.tests.lang.StalePlansTest) fails with java.sql.SQLException: Log Record has been sent to the s

[ https://issues.apache.org/jira/browse/DERBY-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540870 ] Manjula Kutty commented on DERBY-3052: -- Happened again 11/02 with similar stack trace. > testStalePlanCheckInt

[jira] Commented: (DERBY-3083) Network server demands a file called "derbynet.jar" in classpath

[ https://issues.apache.org/jira/browse/DERBY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540871 ] Daniel John Debrunner commented on DERBY-3083: -- To be clear the security manager is trying to secure the

[jira] Commented: (DERBY-3172) ConnectionEventListener.connectionErrorOccurred not being executed when SQLState 08006 Error is thrown

[ https://issues.apache.org/jira/browse/DERBY-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540862 ] Mamta A. Satoor commented on DERBY-3172: I investigated this Jira issue and following is what I found along w

[jira] Assigned: (DERBY-3172) ConnectionEventListener.connectionErrorOccurred not being executed when SQLState 08006 Error is thrown

[ https://issues.apache.org/jira/browse/DERBY-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor reassigned DERBY-3172: -- Assignee: Mamta A. Satoor > ConnectionEventListener.connectionErrorOccurred not being e

[jira] Commented: (DERBY-3083) Network server demands a file called "derbynet.jar" in classpath

[ https://issues.apache.org/jira/browse/DERBY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540856 ] Aaron Digulla commented on DERBY-3083: -- Well, I've used tons of Java software (probably everything kind except f

[jira] Updated: (DERBY-3177) Dropping columns casues auto_increment field to be lost

[ https://issues.apache.org/jira/browse/DERBY-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-3177: --- Attachment: bug2.sql Attached is 'bug2.sql', a modified version of migration-bug.sql in which

[jira] Assigned: (DERBY-3177) Dropping columns casues auto_increment field to be lost

[ https://issues.apache.org/jira/browse/DERBY-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton reassigned DERBY-3177: -- Assignee: Bryan Pendleton > Dropping columns casues auto_increment field to be lost > -

Installing a SecurityManager by default when the server boots

As of release 10.3, when you boot the network server from the command line, the server installs a Java SecurityManager with a default policy. This change (DERBY-2196) limits the ability of hackers, connecting from arbitrary machines, to use Derby to corrupt the environment in which it is runnin

[jira] Issue Comment Edited: (DERBY-3176) J2ME support for phoneME platform disabled in 10.3

[ https://issues.apache.org/jira/browse/DERBY-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540840 ] djd edited comment on DERBY-3176 at 11/7/07 10:57 AM: Well the main reason is

[jira] Commented: (DERBY-3176) J2ME support for phoneME platform disabled in 10.3

[ https://issues.apache.org/jira/browse/DERBY-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540840 ] Daniel John Debrunner commented on DERBY-3176: -- Well the main reason is that is how the code is intended

[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_12540822 ] Anurag Shekhar commented on DERBY-2212: --- >In my opinion ithe functional specification must point that for time

[jira] Commented: (DERBY-3176) J2ME support for phoneME platform disabled in 10.3

[ https://issues.apache.org/jira/browse/DERBY-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540821 ] Rick Hillegas commented on DERBY-3176: -- Thanks for the pointer to derby.env.classes. I will take a look at that.

[jira] Commented: (DERBY-3187) SimpleApp (demo) does not work in a client setting

[ https://issues.apache.org/jira/browse/DERBY-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540820 ] Myrna van Lunteren commented on DERBY-3187: --- I tested that code, with IBM's implementation (weme6.1 - which

[jira] Updated: (DERBY-3175) NullPointerException on INSERT after ALTER TABLE ... DROP COLUMN

[ https://issues.apache.org/jira/browse/DERBY-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-3175: --- Attachment: fixWithTest.diff Attached is "fixWithTest.diff", which incorporates Knut's exampl

[jira] Commented: (DERBY-3185) SET (TRANSACTION) ISOLATION (LEVEL) is not SQL compliant

[ https://issues.apache.org/jira/browse/DERBY-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540813 ] Dyre Tjeldvoll commented on DERBY-3185: --- Hi AB, No you did not misunderstand. That page explains it very well,

[jira] Commented: (DERBY-3176) J2ME support for phoneME platform disabled in 10.3

[ https://issues.apache.org/jira/browse/DERBY-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540809 ] Daniel John Debrunner commented on DERBY-3176: -- The correct fix for the nio problem is for the modules.p

[jira] Commented: (DERBY-3186) Do not allow the user to create inaccessible databases

[ https://issues.apache.org/jira/browse/DERBY-3186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540808 ] Daniel John Debrunner commented on DERBY-3186: -- > The user should not be allowed to set both derby.datab

[jira] Commented: (DERBY-3083) Network server demands a file called "derbynet.jar" in classpath

[ https://issues.apache.org/jira/browse/DERBY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540807 ] Daniel John Debrunner commented on DERBY-3083: -- Note the purpose of the default security manager is to a

Regression Test Report - Daily 592487 - Sun DBTG

[Auto-generated mail] *Daily* 592487/2007-11-06 18:00:13 CET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0287287 073.35% derbyall 097669766 0 1156.43% suitesAll linN+1 0

[jira] Updated: (DERBY-3176) J2ME support for phoneME platform disabled in 10.3

[ https://issues.apache.org/jira/browse/DERBY-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3176: - Attachment: derby-3176-01-phoneME-ac.diff Thanks for the continuing feeback, Dan and John. Attach

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

Issue Subscription Filter: Derby: JIRA issues with patch available (18 issues) Subscriber: derby-dev Key Summary DERBY-3176 J2ME support for phoneME platform disabled in 10.3 https://issues.apache.org/jira/browse/DERBY-3176 DERBY-1272 Change sysinfo to print to error log (de

[jira] Commented: (DERBY-3185) SET (TRANSACTION) ISOLATION (LEVEL) is not SQL compliant

[ https://issues.apache.org/jira/browse/DERBY-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540786 ] A B commented on DERBY-3185: > There is also an inconsistency between JDBC and SQL when specifying > 'repeatable read'

[jira] Updated: (DERBY-3156) Convert testing of derby error stream to JUnit

[ https://issues.apache.org/jira/browse/DERBY-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vemund Østgaard updated DERBY-3156: --- Attachment: 3156-diffv4.stat 3156-diffv4 Thanks again Knut, made a new patch

[jira] Commented: (DERBY-3187) SimpleApp (demo) does not work in a client setting

[ https://issues.apache.org/jira/browse/DERBY-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540763 ] John H. Embretsen commented on DERBY-3187: -- I'm wondering how the DERBY-2216 J2ME change was tested in a J2M

[jira] Updated: (DERBY-3183) 'Error starting tracing' in testTraceCommands(org.apache.derbyTesting.functionTests.tests.derbynet.NetworkServerControlApiTest) on Windows...

[ https://issues.apache.org/jira/browse/DERBY-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3183: --- Environment: OS: Windows JVM: Sun Microsystems Inc. 1.5.0, Sun Microsystems Inc. 1.4.2 was: Window

[jira] Created: (DERBY-3187) SimpleApp (demo) does not work in a client setting

SimpleApp (demo) does not work in a client setting -- Key: DERBY-3187 URL: https://issues.apache.org/jira/browse/DERBY-3187 Project: Derby Issue Type: Sub-task Components: Demos/Scrip

[jira] Updated: (DERBY-3086) The server policy needs to grant derbynet.jar more permissions so that sysinfo and drda tracing will work

[ https://issues.apache.org/jira/browse/DERBY-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick Hillegas updated DERBY-3086: - Attachment: derby-3086-01-morePermissions-ac.diff Attaching derby-3086-01-morePermissions-ac.diff

[jira] Created: (DERBY-3186) Do not allow the user to create inaccessible databases

Do not allow the user to create inaccessible databases -- Key: DERBY-3186 URL: https://issues.apache.org/jira/browse/DERBY-3186 Project: Derby Issue Type: Improvement Reporter:

[jira] Commented: (DERBY-2240) "VALUES expression" is written "VALUES statement" in SelectExpression page of Derby Reference Manual

[ https://issues.apache.org/jira/browse/DERBY-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540759 ] Kim Haase commented on DERBY-2240: -- Thanks very much! > "VALUES expression" is written "VALUES statement" in Selec

[jira] Commented: (DERBY-3156) Convert testing of derby error stream to JUnit

[ https://issues.apache.org/jira/browse/DERBY-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540756 ] Knut Anders Hatlen commented on DERBY-3156: --- Thanks for updating the patch, Vemund. I tried to run the tes

[jira] Commented: (DERBY-3185) SET (TRANSACTION) ISOLATION (LEVEL) is not SQL compliant

[ https://issues.apache.org/jira/browse/DERBY-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540753 ] Bernt M. Johnsen commented on DERBY-3185: - According to SQL 2003, the keyword LEVEL is required too. > SET (

[jira] Commented: (DERBY-2240) "VALUES expression" is written "VALUES statement" in SelectExpression page of Derby Reference Manual

[ https://issues.apache.org/jira/browse/DERBY-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540747 ] Tomohito Nakayama commented on DERBY-2240: -- Committed. Sendingsrc/ref/rrefselectexpression.dita Tra

[jira] Created: (DERBY-3185) SET (TRANSACTION) ISOLATION (LEVEL) is not SQL compliant

SET (TRANSACTION) ISOLATION (LEVEL) is not SQL compliant Key: DERBY-3185 URL: https://issues.apache.org/jira/browse/DERBY-3185 Project: Derby Issue Type: Bug Components: JDBC

[jira] Closed: (DERBY-1769) Add mention that Derby supports rowUpdated, rowDeleted with a result set concurrency of CONCUR_READ_ONLY

[ https://issues.apache.org/jira/browse/DERBY-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik closed DERBY-1769. Resolution: Fixed Fix Version/s: 10.4.0.0 Derby Info: (was: [Patch Available]) Comm

[jira] Updated: (DERBY-1749) Implement Bracketed SQL comments (/*...*/ comments)

[ https://issues.apache.org/jira/browse/DERBY-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-1749: - Assignee: (was: Dag H. Wanvik) Unassiging myself for now. > Implement Bracketed SQL comments

[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_12540728 ] Oleksandr Alesinskyy commented on DERBY-2212: - Anurag, There are still hordes of typos (both in the func

[jira] Commented: (DERBY-3083) Network server demands a file called "derbynet.jar" in classpath

[ https://issues.apache.org/jira/browse/DERBY-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540712 ] Aaron Digulla commented on DERBY-3083: -- Rick: This again breaks the idea of "least surprise". The network server

[jira] Created: (DERBY-3184) Replication: Connection attempts to a database in slave mode must fail

Replication: Connection attempts to a database in slave mode must fail -- Key: DERBY-3184 URL: https://issues.apache.org/jira/browse/DERBY-3184 Project: Derby Issue Type: Su

[jira] Created: (DERBY-3183) 'Error starting tracing' in testTraceCommands(org.apache.derbyTesting.functionTests.tests.derbynet.NetworkServerControlApiTest) on Windows...

'Error starting tracing' in testTraceCommands(org.apache.derbyTesting.functionTests.tests.derbynet.NetworkServerControlApiTest) on Windows... --

[jira] Updated: (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:all-tabpanel ] Anurag Shekhar updated DERBY-2212: -- Attachment: FunctionalSpecV3.html > Add "Unique where not null" to create index > -

[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_12540705 ] Anurag Shekhar commented on DERBY-2212: --- thanks Oleksandr and Øystein for the feed back. In this new version I

[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_12540704 ] Anurag Shekhar commented on DERBY-2212: --- sorry about the duplicate comment. Initially I had added the comment b

[jira] Commented: (DERBY-2872) Add Replication functionality to Derby

[ https://issues.apache.org/jira/browse/DERBY-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540703 ] Jørgen Løland commented on DERBY-2872: -- Replication will be supported in both modes once we get the "connection

[jira] Updated: (DERBY-3161) Test the Derby Replication functionality introduced in DERBY-2872

[ https://issues.apache.org/jira/browse/DERBY-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3161: --- Attachment: README.testReplication README.runningTests README.framewor

[jira] Updated: (DERBY-3161) Test the Derby Replication functionality introduced in DERBY-2872

[ https://issues.apache.org/jira/browse/DERBY-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Solberg updated DERBY-3161: --- Attachment: README.properties > Test the Derby Replication functionality introduced in DERBY-2872 > -