[jira] Updated: (DERBY-1484) Client and embedded behave differently when the table name is null in DatabaseMetaData methods

[ https://issues.apache.org/jira/browse/DERBY-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-1484: - Attachment: DERBY-1484-3.stat DERBY-1484-3.diff The attached patch (3) includes

[jira] Updated: (DERBY-1484) Client and embedded behave differently when the table name is null in DatabaseMetaData methods

[ https://issues.apache.org/jira/browse/DERBY-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-1484: - Derby Info: [Patch Available] Changes undocumented functionality to behave according to

[jira] Commented: (DERBY-1484) Client and embedded behave differently when the table name is null in DatabaseMetaData methods

[ https://issues.apache.org/jira/browse/DERBY-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493591 ] Jørgen Løland commented on DERBY-1484: -- DERBY- *must* be committed before this patch! Client and embedded

Re: limit # rows

Paulo Jesus wrote: Executing a select i get a number of lines.I pretend the firs line returned. No matter if sorted or not. My question come to developers because looks like that the functionality isn't implemented. As the most strait implementation would be by SQL syntax. Or i´m wrong? Did

[jira] Created: (DERBY-2607) DatabaseMetaData is not consistent about throwing SqlException when tablename=null

DatabaseMetaData is not consistent about throwing SqlException when tablename=null -- Key: DERBY-2607 URL: https://issues.apache.org/jira/browse/DERBY-2607 Project:

Re: limit # rows

Hi, This feature request is already recorded as http://issues.apache.org/jira/browse/DERBY-581 -- Bernt Marius Johnsen, Database Technology Group, Staff Engineer, Technical Lead Derby/Java DB Sun Microsystems, Trondheim, Norway signature.asc Description: Digital signature

[jira] Commented: (DERBY-2603) Minor erratum in page of VARCHAR in Derby Reference manual

[ https://issues.apache.org/jira/browse/DERBY-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493599 ] Tomohito Nakayama commented on DERBY-2603: -- Oh. :o I agree that binary in page of Where dynamic parameters

[jira] Commented: (DERBY-2587) Connection.createClob() and Connection.createBlob() need to return locator support enabled LOB objects in the NetworkClient

[ https://issues.apache.org/jira/browse/DERBY-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493607 ] V.Narayanan commented on DERBY-2587: My apologies for this Rick. I got confused with the other errors I

[jira] Created: (DERBY-2608) Compilation Error of manual in Apache FOP

Compilation Error of manual in Apache FOP - Key: DERBY-2608 URL: https://issues.apache.org/jira/browse/DERBY-2608 Project: Derby Issue Type: Bug Components: Build tools, Documentation

[jira] Updated: (DERBY-2608) Compilation Error of manual in Apache FOP

[ https://issues.apache.org/jira/browse/DERBY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomohito Nakayama updated DERBY-2608: - Description: When I compiled whole manual with ant -emacs all command, I encountered

[jira] Commented: (DERBY-2222) 'show indexes in SCHEMANAME' does not work with the client driver

[ https://issues.apache.org/jira/browse/DERBY-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493618 ] Kristian Waagan commented on DERBY-: I'm considering committing the v2 patch, but have a few comments.

[jira] Commented: (DERBY-2608) Compilation Error of manual in Apache FOP

[ https://issues.apache.org/jira/browse/DERBY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493631 ] Tomohito Nakayama commented on DERBY-2608: -- I'm not sure exact reason, but I found that xref element where

[jira] Updated: (DERBY-2608) Compilation Error of manual in Apache FOP

[ https://issues.apache.org/jira/browse/DERBY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomohito Nakayama updated DERBY-2608: - Attachment: DERBY-2608.patch This patch add format attribute whose value is html to xref

[jira] Commented: (DERBY-2608) Compilation Error of manual in Apache FOP

[ https://issues.apache.org/jira/browse/DERBY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493635 ] Tomohito Nakayama commented on DERBY-2608: -- I'm not sure what is this problem is exactly. Error message

[jira] Commented: (DERBY-2608) Compilation Error of manual in Apache FOP

[ https://issues.apache.org/jira/browse/DERBY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493638 ] Tomohito Nakayama commented on DERBY-2608: -- I committed the patch in harry because this error stops other

[jira] Resolved: (DERBY-2608) Compilation Error of manual in Apache FOP

[ https://issues.apache.org/jira/browse/DERBY-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomohito Nakayama resolved DERBY-2608. -- Resolution: Fixed Compilation Error of manual in Apache FOP

[jira] Commented: (DERBY-2192) Translate Derby Reference Manual into Japanese

[ https://issues.apache.org/jira/browse/DERBY-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493654 ] Tomohito Nakayama commented on DERBY-2192: -- It seems that pages for SQL expression was improved on a large

[jira] Updated: (DERBY-2603) Minor erratum in page of VARCHAR in Derby Reference manual

[ https://issues.apache.org/jira/browse/DERBY-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomohito Nakayama updated DERBY-2603: - Attachment: DERBY-2603.patch * Description of the patch * Replace binary to boolean

[jira] Updated: (DERBY-2603) Minor erratum in page of VARCHAR in Derby Reference manual

[ https://issues.apache.org/jira/browse/DERBY-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomohito Nakayama updated DERBY-2603: - Attachment: (was: DERBY-2603.patch) Minor erratum in page of VARCHAR in Derby

[jira] Updated: (DERBY-2603) Minor erratum in page of VARCHAR in Derby Reference manual

[ https://issues.apache.org/jira/browse/DERBY-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomohito Nakayama updated DERBY-2603: - Attachment: DERBY-2603_2.patch Sorry. Previous uploaded patch was one which I found

[jira] Updated: (DERBY-1828) Access rule violations should use a SQL state starting with '42' according to the SQL standard.

[ https://issues.apache.org/jira/browse/DERBY-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-1828: - Attachment: DERBY-1828-2.stat DERBY-1828-2.diff Patch (2) supersedes (1). The

[jira] Updated: (DERBY-2222) 'show indexes in SCHEMANAME' does not work with the client driver

[ https://issues.apache.org/jira/browse/DERBY-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jørgen Løland updated DERBY-: - Derby Info: (was: [Patch Available]) Thanks for reviewing the patch, Kristian. I have made a

[jira] Created: (DERBY-2609) The tests in ij7.sql are only performed in embedded mode.

The tests in ij7.sql are only performed in embedded mode. - Key: DERBY-2609 URL: https://issues.apache.org/jira/browse/DERBY-2609 Project: Derby Issue Type: Sub-task

[jira] Created: (DERBY-2610) Queries in metadata.properties allow tablepattern for JDBC methods that do not allow patterns

Queries in metadata.properties allow tablepattern for JDBC methods that do not allow patterns - Key: DERBY-2610 URL: https://issues.apache.org/jira/browse/DERBY-2610

[jira] Commented: (DERBY-2587) Connection.createClob() and Connection.createBlob() need to return locator support enabled LOB objects in the NetworkClient

[ https://issues.apache.org/jira/browse/DERBY-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493675 ] V.Narayanan commented on DERBY-2587: Thank you for the earlier reviews and comments Rick. The following is my

[jira] Commented: (DERBY-2587) Connection.createClob() and Connection.createBlob() need to return locator support enabled LOB objects in the NetworkClient

[ https://issues.apache.org/jira/browse/DERBY-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493684 ] V.Narayanan commented on DERBY-2587: Knut warned me once about not closing ResultSets in the patch I submitted

[jira] Commented: (DERBY-716) Re-enable VTIs

[ https://issues.apache.org/jira/browse/DERBY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493697 ] Rick Hillegas commented on DERBY-716: - Thanks for helping me puzzle through the usage of VTIEnvironment, Dan. How

ApacheCon '07 presentations (was svn commit: r535247 - in /db/derby/site/trunk: build/site/papers/ApacheCon.html ...)

Thanks for adding the new ApacheCon '07 section with the link to Olav's paper, Knut! -jean [EMAIL PROTECTED] wrote: Author: kahatlen Date: Fri May 4 07:06:45 2007 New Revision: 535247 URL: http://svn.apache.org/viewvc?view=revrev=535247 Log: Added link to the slides from Olav Sandstå's

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

Issue Subscription Filter: Derby: JIRA issues with patch available (20 issues) Subscriber: derby-dev Key Summary DERBY-1001 Rewrite 'store/encryptionKey.sql' to a JUnit test https://issues.apache.org/jira/browse/DERBY-1001 DERBY-1484 Client and embedded behave differently

[jira] Commented: (DERBY-2603) Minor erratum in page of VARCHAR in Derby Reference manual

[ https://issues.apache.org/jira/browse/DERBY-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493725 ] Bryan Pendleton commented on DERBY-2603: I read the _2 version of the patch, applied, and built the doc and

[jira] Commented: (DERBY-2603) Minor erratum in page of VARCHAR in Derby Reference manual

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

[jira] Commented: (DERBY-2604) Implement Clob support for locators

[ https://issues.apache.org/jira/browse/DERBY-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493734 ] Rick Hillegas commented on DERBY-2604: -- Thanks, Naryanan. The patch looks good to me. The tests pass cleanly.

[jira] Commented: (DERBY-2473) Compilation of reference manual translated into pt_BR seems to be failed

[ https://issues.apache.org/jira/browse/DERBY-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493741 ] Tomohito Nakayama commented on DERBY-2473: -- Problem seems to happen in page of Expressões SQL The line

[jira] Updated: (DERBY-2473) Compilation of reference manual translated into pt_BR seems to be failed

[ https://issues.apache.org/jira/browse/DERBY-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomohito Nakayama updated DERBY-2473: - Attachment: refderby.fo Error seems to happen for this file Compilation of

Re: [jira] Updated: (DERBY-1484) Client and embedded behave differently when the table name is null in DatabaseMetaData methods

On 5/3/07, Jørgen Løland (JIRA) [EMAIL PROTECTED] wrote: Changes undocumented functionality to behave according to specification. Hence, I do not think a release note is required. Jørgen, I think a Release note is needed for every change that actually changes behavior - incl. undocumented

[jira] Updated: (DERBY-2606) Derby should print the parameters to failed statements to the derby.log when it logs the error

[ https://issues.apache.org/jira/browse/DERBY-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-2606: -- Attachment: d2602.java Attaching a better java reproduction for this issue. Derby should

[jira] Commented: (DERBY-2473) Compilation of reference manual translated into pt_BR seems to be failed

[ https://issues.apache.org/jira/browse/DERBY-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493754 ] Tomohito Nakayama commented on DERBY-2473: -- I think this problem can be escaped manipulating attributes in

[jira] Updated: (DERBY-2606) Derby should print the parameters to failed statements to the derby.log when it logs the error

[ https://issues.apache.org/jira/browse/DERBY-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-2606: -- Attachment: DERBY_2606_diff.txt attaching a patch to print parameter info to derby.log with

[jira] Updated: (DERBY-2606) Derby should print the parameters to failed statements to the derby.log when it logs the error

[ https://issues.apache.org/jira/browse/DERBY-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden updated DERBY-2606: -- Attachment: DERBY_2606_stat.txt Derby should print the parameters to failed statements to the

[jira] Commented: (DERBY-2473) Compilation of reference manual translated into pt_BR seems to be failed

[ https://issues.apache.org/jira/browse/DERBY-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493761 ] Tomohito Nakayama commented on DERBY-2473: -- It seems that FOP does not support multi column spanned cell

10.3 release translated docs

Hi, Two notices from Tomohito caught my attention, because I've been wondering what to do about the translated documents for a while (ever since we needed to change the licences), and especially more recently since I took on the release management role for 10.3. The first was a remark added to

Re: 10.3 release translated docs

Hello. Through translating referece manual into Japanese, I feel it is very difficult to keep the translated manual up to date for original version. At least, impossible just only with me :( Concening about Japanese, I know Japanese group who translate manuals of Jakarta project into

[jira] Updated: (DERBY-2473) Compilation of reference manual translated into pt_BR seems to be failed

[ https://issues.apache.org/jira/browse/DERBY-2473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomohito Nakayama updated DERBY-2473: - Attachment: DERBY-2473.patch * Description of the patch * Modifying attribute of cell

[jira] Commented: (DERBY-2606) Derby should print the parameters to failed statements to the derby.log when it logs the error

[ https://issues.apache.org/jira/browse/DERBY-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493776 ] Kristian Waagan commented on DERBY-2606: The patch is very simple, and the change also seems like a very

Re: 10.3 release translated docs

Myrna van Lunteren wrote: Hi, Two notices from Tomohito caught my attention, because I've been wondering what to do about the translated documents for a while (ever since we needed to change the licences), and especially more recently since I took on the release management role for 10.3.

[jira] Updated: (DERBY-1816) Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value of zero.

[ https://issues.apache.org/jira/browse/DERBY-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B updated DERBY-1816: --- Attachment: d1816_recycleCleanup_v1.patch While looking into this issue I noticed that there are several methods in

[jira] Assigned: (DERBY-1816) Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value of zero.

[ https://issues.apache.org/jira/browse/DERBY-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A B reassigned DERBY-1816: -- Assignee: A B Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and

[jira] Resolved: (DERBY-2606) Derby should print the parameters to failed statements to the derby.log when it logs the error

[ https://issues.apache.org/jira/browse/DERBY-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden resolved DERBY-2606. --- Resolution: Fixed Fix Version/s: 10.3.0.0 10.2.2.1

[jira] Closed: (DERBY-2606) Derby should print the parameters to failed statements to the derby.log when it logs the error

[ https://issues.apache.org/jira/browse/DERBY-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden closed DERBY-2606. - Derby should print the parameters to failed statements to the derby.log when it logs the error

Re: 10.3 release translated docs

Daniel John Debrunner wrote: Myrna van Lunteren wrote: Hi, Two notices from Tomohito caught my attention, because I've been wondering what to do about the translated documents for a while (ever since we needed to change the licences), and especially more recently since I took on the release

[jira] Assigned: (DERBY-2556) Code paths for db restore do not use doPrivileged-calls, causing SecurityException

[ https://issues.apache.org/jira/browse/DERBY-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kathey Marsden reassigned DERBY-2556: - Assignee: Kathey Marsden Code paths for db restore do not use doPrivileged-calls,

[jira] Commented: (DERBY-1816) Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value of zero.

[ https://issues.apache.org/jira/browse/DERBY-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493804 ] Daniel John Debrunner commented on DERBY-1816: -- The DATE/TIME/TIMESTAMP notes here might help:

Re: ApacheCon '07 presentations (was svn commit: r535247 - in /db/derby/site/trunk: build/site/papers/ApacheCon.html ...)

Jean T. Anderson wrote: Thanks for adding the new ApacheCon '07 section with the link to Olav's paper, Knut! And thanks to Olav for a great presentation! A lot of people showed up at his talk, and judging by the questions from the audience, I think many were very interested in the subject

[jira] Commented: (DERBY-1816) Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value of zero.

[ https://issues.apache.org/jira/browse/DERBY-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493807 ] A B commented on DERBY-1816: Thank you for the link, Dan, it's very helpful. Since all of the changes that I've made in

[jira] Commented: (DERBY-2602) TIMESTAMP value is truncated when return to client

[ https://issues.apache.org/jira/browse/DERBY-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493814 ] A B commented on DERBY-2602: For what little it may be worth, code comments in client/am/PreparedStatement seem to

[jira] Commented: (DERBY-1816) Client's ResultSet.getTime() on a SQL TIMESTAMP column loses the sub-second resolution and always has a milli-second value of zero.

[ https://issues.apache.org/jira/browse/DERBY-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493824 ] Daniel John Debrunner commented on DERBY-1816: -- Note that for getXXX() methods which *do* take a

Re: 10.3 release translated docs

On 5/4/07, Daniel John Debrunner [EMAIL PROTECTED] wrote: Related question, it seems the source distribution does not contain the source for the documentation, any reason for that, or is it simple omission? Omission. This should probably be fixed as part of DERBY-2573, along with improving

[jira] Updated: (DERBY-163) Timestamps do not display trailing zeros

[ https://issues.apache.org/jira/browse/DERBY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew McIntyre updated DERBY-163: -- Summary: Timestamps do not display trailing zeros (was: Timestamp formatting) Timestamps do

[jira] Resolved: (DERBY-2611) upgrade test incorrectly tries to test in place compress in 10.0 release.

[ https://issues.apache.org/jira/browse/DERBY-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali resolved DERBY-2611. --- Resolution: Fixed Fix Version/s: 10.3.0.0 checkin 535429 fixes the two errors from

[jira] Created: (DERBY-2612) running soft upgrade of a 10.0 database vs. 10.3 software gives test error in testGetTablesModify concerning XML type

running soft upgrade of a 10.0 database vs. 10.3 software gives test error in testGetTablesModify concerning XML type -- Key: DERBY-2612 URL:

Re: it looks like the public posting web site for test results from IBM is broken

On 4/15/07, Andrew McIntyre [EMAIL PROTECTED] wrote: On 4/15/07, Jean T. Anderson [EMAIL PROTECTED] wrote: I don't think we should remove the link as it does contain history which is still correct. Though maybe a note should be added that new data is not being added. I think that

[jira] Closed: (DERBY-1919) Top level index.html page should link to release notes and other items in top-level of a release.

[ https://issues.apache.org/jira/browse/DERBY-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew McIntyre closed DERBY-1919. -- Resolution: Fixed Assignee: Rick Hillegas Fixed by Rick, changes committed to trunk and

[jira] Commented: (DERBY-2373) Upgrade documentation PDF builds to use FOP .93

[ https://issues.apache.org/jira/browse/DERBY-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493840 ] Andrew McIntyre commented on DERBY-2373: Most of the warnings seen with the new FOP build are identical to

[jira] Created: (DERBY-2613) upgrade test problem when attempting to test 10.0.2.1 -

upgrade test problem when attempting to test 10.0.2.1 - Key: DERBY-2613 URL: https://issues.apache.org/jira/browse/DERBY-2613 Project: Derby Issue Type: Bug Components:

[jira] Updated: (DERBY-2613) upgrade test problem when attempting to test 10.0.2.1 -

[ https://issues.apache.org/jira/browse/DERBY-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-2613: -- problem also reproduces if only 10.0.2.1/lib exists in the directory path of jars to test.

[jira] Created: (DERBY-2614) improve upgrade junit test to not lose info written to derby.log

improve upgrade junit test to not lose info written to derby.log Key: DERBY-2614 URL: https://issues.apache.org/jira/browse/DERBY-2614 Project: Derby Issue Type: Improvement

nested exceptions and junit tests?

Is the printing of nested exceptions a problem with my junit test runner, our junit test, or something else. When running upgrade tests my test runner gets the following which is pretty useless without the following/nested exception: 2) Upgrade Phase: UPGRADEjava.sql.SQLException: Failed to

[jira] Updated: (DERBY-2612) running soft upgrade of a 10.0 database vs. 10.3 software gives test error in testGetTablesModify concerning XML type

[ https://issues.apache.org/jira/browse/DERBY-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-2612: -- this problem also reproduces when only 10.0 jars are in the upgrade test path. running soft

[jira] Updated: (DERBY-2613) upgrade test problem when attempting to test 10.0.2.1 -

[ https://issues.apache.org/jira/browse/DERBY-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-2613: -- I only took a quick look at this, but it looks like the code to upgrade a 10.0 database first

[jira] Assigned: (DERBY-2613) upgrade test problem when attempting to test 10.0.2.1 -

[ https://issues.apache.org/jira/browse/DERBY-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali reassigned DERBY-2613: - Assignee: Mike Matrigali upgrade test problem when attempting to test 10.0.2.1 -

build error -- derby 10.2.2.0

Hello, While trying to build derby 10.2.2.0, I got the following errors. I followed the instructions in DUILDING.txt file. -ant.properties j13lib=/usr/java/jdk1.3.1_20/jre/lib/ j14lib=/usr/java/j2sdk1.4.2_14/jre/lib/ build.compiler=jikes proceed=true sane=false

[jira] Assigned: (DERBY-2019) IJ's describe command does not handle quotes very well

[ https://issues.apache.org/jira/browse/DERBY-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton reassigned DERBY-2019: -- Assignee: Bryan Pendleton IJ's describe command does not handle quotes very well