Re: Regression Test Failure! - TinderBox_Derby 433085 - Sun DBTG

[EMAIL PROTECTED] wrote: [Auto-generated mail] *TinderBox_Derby* 433085/2006-08-21 01:22:24 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 2672670 2 154.08% SunOS-5.10_i86pc-i386

[jira] Created: (DERBY-1736) Additonal Grant and Revoke tests

Additonal Grant and Revoke tests Key: DERBY-1736 URL: http://issues.apache.org/jira/browse/DERBY-1736 Project: Derby Issue Type: Test Components: Test Affects Versions: 10.2.1.0

[jira] Assigned: (DERBY-1736) Additonal Grant and Revoke tests

[ http://issues.apache.org/jira/browse/DERBY-1736?page=all ] Yip Ng reassigned DERBY-1736: - Assignee: Yip Ng Additonal Grant and Revoke tests Key: DERBY-1736 URL:

[jira] Commented: (DERBY-1708) Unprivileged user can perform lock table statement on a table which he/she does not have any access rights

[ http://issues.apache.org/jira/browse/DERBY-1708?page=comments#action_12429358 ] Yip Ng commented on DERBY-1708: --- derbyall passes, no new regression introduced with this patch. Unprivileged user can perform lock table statement on a table which

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429361 ] Andreas Korneliussen commented on DERBY-418: I think that the lack of synchronization when calling singleUseActivation.markUnused() may cause that

[jira] Resolved: (DERBY-1712) Add a JUnit test decorator that starts the NetworkServer at setUp and stops it at tearDown.

[ http://issues.apache.org/jira/browse/DERBY-1712?page=all ] Andreas Korneliussen resolved DERBY-1712. - Resolution: Fixed Add a JUnit test decorator that starts the NetworkServer at setUp and stops it at tearDown.

[jira] Closed: (DERBY-1712) Add a JUnit test decorator that starts the NetworkServer at setUp and stops it at tearDown.

[ http://issues.apache.org/jira/browse/DERBY-1712?page=all ] Andreas Korneliussen closed DERBY-1712. --- Add a JUnit test decorator that starts the NetworkServer at setUp and stops it at tearDown.

Regression Test Failure! - Derby 432992 - Sun DBTG

[Auto-generated mail] *Derby* 432992/2006-08-20 19:46:04 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.6* 3715712 0 110.71% SunOS-5.10_i86pc-i386 Details in

[jira] Updated: (DERBY-1558) enable more testcases in ConcurrencyTest

[ http://issues.apache.org/jira/browse/DERBY-1558?page=all ] Andreas Korneliussen updated DERBY-1558: Attachment: DERBY-1558.diff DERBY-1558.stat Attaching patch which enables more testcases in ConcurrencyTest. The patch makes

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429368 ] Knut Anders Hatlen commented on DERBY-1610: --- There will be user impact even if only a few of the incompatible combinations are changed to throw

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429374 ] Tomohito Nakayama commented on DERBY-1610: -- I see I think opinion of Knut is proper. I will rollback DERBY-1535. Then, this task is regarded as

[jira] Commented: (DERBY-1693) Out of Memory Error with derby.language.logStatementText=true

[ http://issues.apache.org/jira/browse/DERBY-1693?page=comments#action_12429382 ] Kristian Waagan commented on DERBY-1693: I agree that the values for LOBs should not be printed. The question is what should be printed instead? I would go

[jira] Commented: (DERBY-1547) Add svn version number to DatabaseMetaData getDatabaseProductVersion and getDriverVersion() to improve supportability

[ http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12429383 ] V.Narayanan commented on DERBY-1547: The four kinds of pattern strings that need to be searched for in the tests output while solving this are the following

[jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12429384 ] Tomohito Nakayama commented on DERBY-1559: -- Hello, Andreas. Discussion in DERBY-1610 resulted to the answer that we need to solve DERBY-1610 before

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429386 ] Andreas Korneliussen commented on DERBY-418: The finalizer thread is as pr javadoc guaranteed to not hold any user-visible synchronization locks when

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429387 ] Tomohito Nakayama commented on DERBY-1610: -- I think we need to fix the range of modification. My plan is making compatibility around setBlob(notNull/null)

[jira] Updated: (DERBY-1633) Regression: The fields of views are not being calculated properly since 10.1.2.4

[ http://issues.apache.org/jira/browse/DERBY-1633?page=all ] A B updated DERBY-1633: --- Attachment: d1633_v3_code.patch d1633_v3_tests.patch DERBY-1633_v3.html Attaching a third attempt at resolving this issue, d1633_v3_code.patch

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429390 ] Tomohito Nakayama commented on DERBY-1610: -- I meant setBinaryStream(notNull/null) also ... Updating column typed as CHAR to value passed via

[jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12429394 ] Andreas Korneliussen commented on DERBY-1559: - DERBY-1535 caused conflicts with this patch during development. Now, DERBY-1610 will cause conflicts

[jira] Updated: (DERBY-1387) Add JMX extensions to Derby

[ http://issues.apache.org/jira/browse/DERBY-1387?page=all ] Sanket Sharma updated DERBY-1387: - Attachment: derbyjmx.patch Submitting The Code for Derby's JMX Functionality as part of my Google SOC project. The patch addresses the following: 1)

The JMX code is available for review

Hi, As part of my Google SOC project, I've uploaded the JMX code for review in Jira. Please note the following: The patch addresses the following: 1) Start derby with monitoring extensions enabled. To start derby with monitoring extensions, you need to set derby.jmx environment variable while

[jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12429403 ] Tomohito Nakayama commented on DERBY-1559: -- Well. If *you* don't think the difference of DerbyNetClient/parameterMapping.out is critically harmful,

[jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

[ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12429406 ] Andreas Korneliussen commented on DERBY-1559: - I will wait for DERBY-1610 being fixed, to avoid the risk. when receiving a single EXTDTA object

Re: [jira] Commented: (DERBY-1559) when receiving a single EXTDTA object representing a BLOB, the server do not need to read it into memory before inserting it into the DB

Hello. Thank you for your carefulness. Please give your watch on DERBY-1610 and decide when you commit DERBY-1559. Best regards. Andreas Korneliussen (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1559?page=comments#action_12429406 ] Andreas Korneliussen commented

[jira] Commented: (DERBY-1535) Trial 2 for DERBY-550, improve use of Engine from NetworkServer and reduce memory usage

[ http://issues.apache.org/jira/browse/DERBY-1535?page=comments#action_12429415 ] Tomohito Nakayama commented on DERBY-1535: -- Now, I'm preparing to rollback DERBY-1513_1535_2.patch. Please see more information in DERBY-1610. Trial 2

Re: [jira] Resolved: (DERBY-1717) Working With Derby task file twwdactivity4.dita is invalid, results in missing text

Great -- thank you very much. Kim Knut Anders Hatlen (JIRA) wrote On 08/18/06 19:14,: [ http://issues.apache.org/jira/browse/DERBY-1717?page=all ] Knut Anders Hatlen resolved DERBY-1717. --- Resolution: Fixed Derby Info: (was: [Patch

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429416 ] Tomohito Nakayama commented on DERBY-1610: -- By the way, is it really possible to judge the type checks on the client side ? There are only less

Re: Cache Manager: Summer Progress

Gokul Soundararajan wrote: I have placed the code and report on my website at: Report http://www.eecg.toronto.edu/~gokul/derby/derby-report-aug-19-2006.pdf Code http://www.eecg.toronto.edu/~gokul/derby/code/aug-19-2006/ Gokul, Thank you very much for your work so far. It would be nice if

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429424 ] Knut Anders Hatlen commented on DERBY-1610: --- Yes, I think you can decide the correct type on the client side. ParameterMetaData (which can be obtained

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429425 ] Tomohito Nakayama commented on DERBY-1610: -- Regarding check on the client side, I found description of PRPSQLSTT in the spec of drda. It seems that

[jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBinarySt

[ http://issues.apache.org/jira/browse/DERBY-1610?page=comments#action_12429427 ] Tomohito Nakayama commented on DERBY-1610: -- Oh... Our comments were conflicted :) I see. Anyway it seems that I need to work on current implementation of

Re: Regression Test Failure! - TinderBox_Derby 433085 - Sun DBTG

Oystein Grovlen - Sun Norway wrote: [EMAIL PROTECTED] wrote: [Auto-generated mail] *TinderBox_Derby* 433085/2006-08-21 01:22:24 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 2672670

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429430 ] Daniel John Debrunner commented on DERBY-418: - I don't think there is any guarantee about the order of finalization, therefore it is impossible to

Re: [jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBina

Hello Knut. By the way, I want to figure it out what is the actual range of modification in DERBY-1610. Knut Anders Hatlen commented on DERBY-1610: Therefore, I think that it is better to fix all of them at once. What is all of them here ? Just setBlob and setBinaryStream ? Or whole case

[jira] Updated: (DERBY-1535) Trial 2 for DERBY-550, improve use of Engine from NetworkServer and reduce memory usage

[ http://issues.apache.org/jira/browse/DERBY-1535?page=all ] Tomohito Nakayama updated DERBY-1535: - Attachment: DERBY-1513_1535_rollback.patch Description of the patch : Rollback DERBY-1513_1535_2.patch. Test of the patch : Execute derbyall

[jira] Commented: (DERBY-1387) Add JMX extensions to Derby

[ http://issues.apache.org/jira/browse/DERBY-1387?page=comments#action_12429432 ] Andreas Korneliussen commented on DERBY-1387: - Hi, thanks for providing this patch. I have tried compiling it, and I do have the following comments:

Re: [jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBina

Tomohito Nakayama commented on DERBY-1610: -- Oh... Our comments were conflicted :) I see. Anyway it seems that I need to work on current implementation of NetworkClient. I will try. Great! One extra benefit we get when we have the type check on

[jira] Updated: (DERBY-1633) Regression: The fields of views are not being calculated properly since 10.1.2.4

[ http://issues.apache.org/jira/browse/DERBY-1633?page=all ] A B updated DERBY-1633: --- Derby Info: [Patch Available, Existing Application Impact, Regression] (was: [Existing Application Impact, Regression]) Regression: The fields of views are not being

Re: [jira] Commented: (DERBY-1387) Add JMX extensions to Derby

On 8/21/06, Andreas Korneliussen (JIRA) derby-dev@db.apache.org wrote: [ http://issues.apache.org/jira/browse/DERBY-1387?page=comments#action_12429432 ] Andreas Korneliussen commented on DERBY-1387: - Hi, thanks for providing this patch. I have

Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.

Andrew McIntyre wrote: On 8/20/06, Satheesh Bandaram (JIRA) derby-dev@db.apache.org wrote: 3) Looks like the code uses generics, which limit the use to JDK 1.5 platforms. While this may be ok, need to document need for JDK 1.5 platform and raise appropriate message if used in earlier

[jira] Updated: (DERBY-1730) Manifest file doesn't contain OSGi attributes

[ http://issues.apache.org/jira/browse/DERBY-1730?page=all ] Rick Hillegas updated DERBY-1730: - Urgency: Urgent (was: Normal) Manifest file doesn't contain OSGi attributes - Key:

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

Issue Subscription Filter: Derby: JIRA issues with patch available (22 issues) Subscriber: derby-dev Key Summary DERBY-1633 Regression: The fields of views are not being calculated properly since 10.1.2.4 http://issues.apache.org/jira/browse/DERBY-1633 DERBY-1559 when

[jira] Created: (DERBY-1737) Network Server should check for current open and active connections before shutting down a database

Network Server should check for current open and active connections before shutting down a database --- Key: DERBY-1737 URL:

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429438 ] Andreas Korneliussen commented on DERBY-418: I am not sure what you mean. Could you give an example ? I agree that it is possible to get a deadlock

drop column functionality

This is a continuation of a discussion on the users mailing list which I was advised to transfer here. See: http://thread.gmane.org/gmane.comp.apache.db.derby.user/4836/focus=4836 I've applied the patch for dropping columns and confirmed it works in a basic scenario. Here are some follow

Re: 10.2 branch version number wrong?

Hi Dan, Thanks for pointing this out. I will bump the last digit now. Regards, -Rick Daniel John Debrunner wrote: Since there was a snapshot off the 10.2 branch, shouldn't its current version be 10.2.1.1 beta? I thought after a snapshot the normal practice was to bump the last digit. Maybe

Re: [jira] Commented: (DERBY-1387) Add JMX extensions to Derby

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sanket Sharma wrote: On 8/21/06, Andreas Korneliussen (JIRA) derby-dev@db.apache.org wrote: [ http://issues.apache.org/jira/browse/DERBY-1387?page=comments#action_12429432 ] Andreas Korneliussen commented on DERBY-1387:

[jira] Updated: (DERBY-1678) Track changes to 10.2 branch needed to build candidates

[ http://issues.apache.org/jira/browse/DERBY-1678?page=all ] Rick Hillegas updated DERBY-1678: - Attachment: derby-1678-10.2-bumpVersionNumbers_v03.diff Committing derby-1678-10.2-bumpVersionNumbers_v03.diff, bumping the last digit of the version id

Re: beta snapshot download from the website

Jean T. Anderson wrote: Rick Hillegas wrote: ... Also noticed that on the download page in the left panel, derby 10.1.2.1 is listed instead of 10.1.3.1. Good catch -- and where to correct that isn't obvious. Here is the file: derby/site/trunk/src/documentation/content/xdocs/site.xml

[jira] Reopened: (DERBY-1622) Add documentation for encrypted database using encryptionKey

[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ] Laura Stewart reopened DERBY-1622: -- Need to add one more fix Add documentation for encrypted database using encryptionKey

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429442 ] Daniel John Debrunner commented on DERBY-418: - The alternate way to phrase it is: Can you guarantee no deadlocks from using synchronization in the

[jira] Updated: (DERBY-1622) Add documentation for encrypted database using encryptionKey

[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ] Laura Stewart updated DERBY-1622: - Attachment: derby1622_html5.zip derby1622_devguide_5.diff Updated file tdevdvlp40140 per comments received. I thought that file

[jira] Updated: (DERBY-1622) Add documentation for encrypted database using encryptionKey

[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ] Laura Stewart updated DERBY-1622: - Derby Info: [Patch Available] Add documentation for encrypted database using encryptionKey

Re: [jira] Updated: (DERBY-1622) Add documentation for encrypted database using encryptionKey

Laura Stewart (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1622?page=all ] Laura Stewart updated DERBY-1622: - Attachment: derby1622_html5.zip derby1622_devguide_5.diff Updated file tdevdvlp40140 per comments

[jira] Commented: (DERBY-1622) Add documentation for encrypted database using encryptionKey

[ http://issues.apache.org/jira/browse/DERBY-1622?page=comments#action_12429448 ] Sunitha Kambhampati commented on DERBY-1622: Thanks Laura for the updates. Changes in derby1622_html5.zip look good and can be committed. Add

[jira] Commented: (DERBY-1717) Working With Derby task file twwdactivity4.dita is invalid, results in missing text

[ http://issues.apache.org/jira/browse/DERBY-1717?page=comments#action_12429449 ] Stan Bradbury commented on DERBY-1717: -- Better late than never: I reviewed the revised section and the rework looks great. Thanks Kim for your attention in

Re: drop column functionality

1. Dropping the column seems very slow for large tables. This is good to know. I don't think anybody has really experimented with this yet. Can you quantify very slow with some real measurements you've taken? Do you think it would be reasonable to treat this as a follow-on improvement to the

[jira] Resolved: (DERBY-1622) Add documentation for encrypted database using encryptionKey

[ http://issues.apache.org/jira/browse/DERBY-1622?page=all ] Jean T. Anderson resolved DERBY-1622. - Fix Version/s: 10.3.0.0 (was: 10.2.1.0) Resolution: Fixed Derby Info: (was: [Patch Available]) Committed patch

[jira] Commented: (DERBY-1655) Document XML functionality for 10.2

[ http://issues.apache.org/jira/browse/DERBY-1655?page=comments#action_12429467 ] A B commented on DERBY-1655: Thank you Laura for taking the time to port the doc changes in _v1.html into the Derby 10.2 manuals. The changes in:

Re: [jira] Commented: (DERBY-1655) Document XML functionality for 10.2

A B (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1655?page=comments#action_12429467 ] A B commented on DERBY-1655: Thank you Laura for taking the time to port the doc changes in _v1.html into the Derby 10.2 manuals. The

[jira] Created: (DERBY-1738) An user is able to grant select privilege on a view but the underlying object is not own by the user.

An user is able to grant select privilege on a view but the underlying object is not own by the user. -- Key: DERBY-1738 URL:

Re: Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.

On 8/21/06, Daniel John Debrunner [EMAIL PROTECTED] wrote: Andrew McIntyre wrote: On 8/20/06, Satheesh Bandaram (JIRA) derby-dev@db.apache.org wrote: 3) Looks like the code uses generics, which limit the use to JDK 1.5 platforms. While this may be ok, need to document need for JDK 1.5

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429473 ] Andreas Korneliussen commented on DERBY-418: Assuming the Derby embedded JDBC driver is thread-safe, it should be safe for a result set to call its own

[jira] Commented: (DERBY-1655) Document XML functionality for 10.2

[ http://issues.apache.org/jira/browse/DERBY-1655?page=comments#action_12429474 ] Jean T. Anderson commented on DERBY-1655: - Committed to the trunk derby1655_tuning.diff (revision 433298) and derby1655_tools_html.diff (revision 433307).

Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.

Andrew McIntyre wrote: On 8/21/06, Daniel John Debrunner [EMAIL PROTECTED] wrote: Andrew McIntyre wrote: On 8/20/06, Satheesh Bandaram (JIRA) derby-dev@db.apache.org wrote: 3) Looks like the code uses generics, which limit the use to JDK 1.5 platforms. While this may be ok, need to

[jira] Commented: (DERBY-1655) Document XML functionality for 10.2

[ http://issues.apache.org/jira/browse/DERBY-1655?page=comments#action_12429477 ] Laura Stewart commented on DERBY-1655: -- Hi Army - I am working on updating the dev guide now and will include these comments for the ref manual. I should

[jira] Commented: (DERBY-1547) Add svn version number to DatabaseMetaData getDatabaseProductVersion and getDriverVersion() to improve supportability

[ http://issues.apache.org/jira/browse/DERBY-1547?page=comments#action_12429478 ] Andrew McIntyre commented on DERBY-1547: The above solution has been based on the suggestions received for this issue in using a property file as the

[jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

[ http://issues.apache.org/jira/browse/DERBY-418?page=comments#action_12429483 ] Daniel John Debrunner commented on DERBY-418: - I'd assumed that you were going to go in at a lower level than ResultSet.close(). ResultSet.close() is

Documentation Style Issue - semi-colon at the end of SQL statement examples

Hi - Should there be a semi-colon at the end of the SQL statement examples in the Derby documentation. In other documentation work that I have done, this was the standard. I just wanted to check with the Derby community to see what is appropriate for the Derby docs. -- Laura Stewart

Re: Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.

On 8/21/06, Daniel John Debrunner [EMAIL PROTECTED] wrote: That is actually engine code, so should not be used by the tools (or the tests) Yet there are references to JVMInfo in both ij and sysinfo. Should these be removed, then? it would work for some cases (assuming the code was moved),

Regression Test Failure! - TinderBox_Derby 433261 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 433261/2006-08-21 17:22:24 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 1672671 2 149.26% SunOS-5.10_i86pc-i386 Details in

[jira] Commented: (DERBY-1655) Document XML functionality for 10.2

[ http://issues.apache.org/jira/browse/DERBY-1655?page=comments#action_12429486 ] Laura Stewart commented on DERBY-1655: -- Regarding the new information about XMLEXISTS, you ask that it be put into the Built-in function section and yet you

Re: [jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

Andreas Korneliussen (JIRA) derby-dev@db.apache.org writes: Assuming the Derby embedded JDBC driver is thread-safe, it should be safe for a result set to call its own close() method in its finalizer. If you get a dead-lock in the finalizer, it proves that it is also possible to write a

Re: [jira] Commented: (DERBY-1651) Develop a mechanism to migrate mySQL databases to Derby. Migration tool should include both schema and data migration options.

Andrew McIntyre wrote: On 8/21/06, Daniel John Debrunner [EMAIL PROTECTED] wrote: That is actually engine code, so should not be used by the tools (or the tests) Yet there are references to JVMInfo in both ij and sysinfo. Should these be removed, then? Or the code moved into the

[jira] Commented: (DERBY-1292) ClassCastException in ClientDriver when using CLOB columns and batch updates

[ http://issues.apache.org/jira/browse/DERBY-1292?page=comments#action_12429487 ] James F. Adams commented on DERBY-1292: --- The uploaded patch is ready for review. ClassCastException in ClientDriver when using CLOB columns and batch

[jira] Commented: (DERBY-1738) An user is able to grant select privilege on a view but the underlying object is not own by the user.

[ http://issues.apache.org/jira/browse/DERBY-1738?page=comments#action_12429488 ] Satheesh Bandaram commented on DERBY-1738: -- This is a duplicate of the issue Rajesh has already filed. I think that is DERBY-1686. An user is able to

Re: [jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

Knut Anders Hatlen wrote: Andreas Korneliussen (JIRA) derby-dev@db.apache.org writes: Assuming the Derby embedded JDBC driver is thread-safe, it should be safe for a result set to call its own close() method in its finalizer. If you get a dead-lock in the finalizer, it proves that it is

Re: [jira] Commented: (DERBY-418) outofmemory error when running large query in autocommit=false mode

Not sure of the guarantee of the unsynchronized field being set. Are you saying that field will never be seen as set, or that the setting may not be seen for some time? It may be seen, however it may also never be seen. Andreas

[jira] Commented: (DERBY-1655) Document XML functionality for 10.2

[ http://issues.apache.org/jira/browse/DERBY-1655?page=comments#action_12429495 ] A B commented on DERBY-1655: Okay to refer to it as a function instead of an operator? Great question. I guess I'm not sure what the answer here should be... I've

Re: [jira] Commented: (DERBY-1610) Updating column typed as CHAR to value passed via setBinaryStream(notNull) is failed because of imcompatiblity of types though it was not taken as error when setBina

TomohitoNakayama [EMAIL PROTECTED] writes: Hello Knut. By the way, I want to figure it out what is the actual range of modification in DERBY-1610. Knut Anders Hatlen commented on DERBY-1610: Therefore, I think that it is better to fix all of them at once. What is all of them here ? Just

Re: Documentation Style Issue - semi-colon at the end of SQL statement examples

Laura Stewart wrote: Hi - Should there be a semi-colon at the end of the SQL statement examples in the Derby documentation. In other documentation work that I have done, this was the standard. I just wanted to check with the Derby community to see what is appropriate for the Derby docs. I

[jira] Commented: (DERBY-1674) Investigate reducing the number of classes methods in DataDictionary used to represent system tables

[ http://issues.apache.org/jira/browse/DERBY-1674?page=comments#action_12429501 ] Daniel John Debrunner commented on DERBY-1674: -- Simple stats on class count and sizes in insane mode (from the classes folder, not size in the jar).

Re: Documentation Style Issue - semi-colon at the end of SQL statement examples

Laura Stewart [EMAIL PROTECTED] writes: Hi - Should there be a semi-colon at the end of the SQL statement examples in the Derby documentation. In other documentation work that I have done, this was the standard. I just wanted to check with the Derby community to see what is appropriate for

[jira] Updated: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh updated DERBY-1582: Derby Info: [Patch Available] REVOKE statement does not generate a warning when no privileges are revoked.

[jira] Updated: (DERBY-1582) REVOKE statement does not generate a warning when no privileges are revoked.

[ http://issues.apache.org/jira/browse/DERBY-1582?page=all ] Deepa Remesh updated DERBY-1582: Attachment: d1582_v2_with_tests.diff Attaching patch 'd1582_v2_with_tests.diff' which raises a warning when no privileges are revoked by the revoke statement

[jira] Closed: (DERBY-1738) An user is able to grant select privilege on a view but the underlying object is not own by the user.

[ http://issues.apache.org/jira/browse/DERBY-1738?page=all ] Yip Ng closed DERBY-1738. - Resolution: Duplicate Duplicate to DERBY-1686, link DERBY-1686 to DERBY-1330. An user is able to grant select privilege on a view but the underlying object is not own by

Re: drop column functionality

On 8/21/06, Bryan Pendleton [EMAIL PROTECTED] wrote: 3. The version from trunk does not appear able to read databases created with the 10.1.3.1 release. Has the database file syntax changed? I'm hoping one of the other developers can help with this question. I think that this is on purpose,

[jira] Created: (DERBY-1739) Index column names in CatalogRowFactory implementations are not required

Index column names in CatalogRowFactory implementations are not required Key: DERBY-1739 URL: http://issues.apache.org/jira/browse/DERBY-1739 Project: Derby Issue

[jira] Commented: (DERBY-1734) Simplify building of SystemColumn array in CatalogRowFactory implementations.

[ http://issues.apache.org/jira/browse/DERBY-1734?page=comments#action_12429518 ] Daniel John Debrunner commented on DERBY-1734: -- 5) No requirement to convert the case for column names, these classes are for Derby's implementation

Re: Mustang license (was Re: spec license updated, looks good ...)

I want to keep the community informed on where this issue stands right now. The short story is that the lawyers are still working on some solution which will allow us to build our JDBC4 drivers even though Java SE 6 is still in beta. The lawyers know that we want to build a release candidate

[jira] Commented: (DERBY-1633) Regression: The fields of views are not being calculated properly since 10.1.2.4

[ http://issues.apache.org/jira/browse/DERBY-1633?page=comments#action_12429520 ] A B commented on DERBY-1633: I applied the _v3 patches and ran derbyall on Red Hat Linux with ibm142 against sane jars with no new failures. So as mentioned in my

[jira] Updated: (DERBY-688) Enhancements to XML functionality to move toward XPath/XQuery support...

[ http://issues.apache.org/jira/browse/DERBY-688?page=all ] A B updated DERBY-688: -- Attachment: d688_phase6_v1.patch Attaching a phase 6 patch, d688_phase6_v1.patch, that changes the SQLSTATEs for XML errors to match the SQL/XML specification where possible, and

[jira] Updated: (DERBY-688) Enhancements to XML functionality to move toward XPath/XQuery support...

[ http://issues.apache.org/jira/browse/DERBY-688?page=all ] A B updated DERBY-688: -- Derby Info: [Patch Available] Enhancements to XML functionality to move toward XPath/XQuery support...

[jira] Created: (DERBY-1740) Change error message to indicate encryptionkey length to be atleast 16 characters instead of 8 characters

Change error message to indicate encryptionkey length to be atleast 16 characters instead of 8 characters - Key: DERBY-1740 URL:

Regarding getting old snapshots of 10.2 ( was Re: 10.1.2.4 snapshot posted)

Andrew McIntyre wrote: On 5/10/06, Daniel John Debrunner [EMAIL PROTECTED] wrote: However, I think when a snapshot is posted we should leave the older snapshots on the download page. Makes it much easier for people to demonstrate a regression if they can easily show it's in the latest

Re: drop column functionality

Deepa Remesh wrote: On 8/21/06, Bryan Pendleton [EMAIL PROTECTED] wrote: 3. The version from trunk does not appear able to read databases created with the 10.1.3.1 release. Has the database file syntax changed? I'm hoping one of the other developers can help with this question. I

Re: Regarding getting old snapshots of 10.2 ( was Re: 10.1.2.4 snapshot posted)

On 8/21/06, Sunitha Kambhampati [EMAIL PROTECTED] wrote: Are the snapshot jars stored in svn someplace ? Where can I get them from. It would be great if you can point me to the link. The jars are stored in svn with the website, in the site tree. You can run svn log on build/site/binaries in

Re: Regarding getting old snapshots of 10.2 ( was Re: 10.1.2.4 snapshot posted)

Hi Sunitha, The 10.2.0.4 alpha snapshot is still visible from the downloads page. You can get ahold of an older snapshot than that, although it's not pretty. The snapshots hang off the Derby website and so are checked into the Derby website repository. You need to create a subversion client

Regression Test Failure! - TinderBox_Derby 433317 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 433317/2006-08-21 20:32:59 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 1672671 2 155.29% SunOS-5.10_i86pc-i386 Details in

Re: Regarding getting old snapshots of 10.2 ( was Re: 10.1.2.4 snapshot posted)

Andrew McIntyre wrote: or use viewvc to get a download link without having to check out the site tree. That helps. Thanks Andrew and Rick. Sunitha.

  1   2   >