[ http://issues.apache.org/jira/browse/DERBY-1792?page=all ]
Rick Hillegas updated DERBY-1792:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Move to 10.2.3.0.
> Have the buildjars target layut the jars identically to a distribution, wi
[ http://issues.apache.org/jira/browse/DERBY-1801?page=all ]
Rick Hillegas updated DERBY-1801:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Move to 10.2.3.0.
> Reoccurrence of JIRA-937: Instability in wisconsin test
>
[ http://issues.apache.org/jira/browse/DERBY-1806?page=all ]
Rick Hillegas updated DERBY-1806:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Move to 10.2.3.0.
> Connection errors in 10.2.1.1 - not seen in 10.1.2.1
> ---
[ http://issues.apache.org/jira/browse/DERBY-1807?page=all ]
Rick Hillegas updated DERBY-1807:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Move to 10.2.3.0.
> Run more grant/revoke tests on an upgraded database
>
Hello.
I'm afraid that your case is not addressed yet ...
Several improvement around memory usage for LOB was achieved / is under
work.
But I think memory usage in NetworkClient driver when receiving LOB from
NetworkServer is not improved yet.
If you don't mind, could you tell us your case i
[ http://issues.apache.org/jira/browse/DERBY-1868?page=all ]
Rick Hillegas updated DERBY-1868:
-
Fix Version/s: 10.3.0.0
(was: 10.2.2.0)
Reassigning to 10.3 since that's where the work will show up.
> Merge argument descriptors int
[ http://issues.apache.org/jira/browse/DERBY-1920?page=all ]
Rick Hillegas updated DERBY-1920:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Reassign to 10.2.3.0.
> DOCS - Improve topic titles for vague and duplicate topics
> -
[ http://issues.apache.org/jira/browse/DERBY-1921?page=all ]
Rick Hillegas closed DERBY-1921.
> Bring STATUS file up to date
>
>
> Key: DERBY-1921
> URL: http://issues.apache.org/jira/browse/DERBY-
[ http://issues.apache.org/jira/browse/DERBY-1921?page=all ]
Rick Hillegas resolved DERBY-1921.
--
Resolution: Fixed
> Bring STATUS file up to date
>
>
> Key: DERBY-1921
> URL: http://issues.apa
[ http://issues.apache.org/jira/browse/DERBY-1932?page=all ]
Rick Hillegas updated DERBY-1932:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Reassigning to 10.2.3.0.
> Reference Manual updates - JDBC Reference section
> ---
[ http://issues.apache.org/jira/browse/DERBY-1934?page=all ]
Rick Hillegas updated DERBY-1934:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Reassigning to 10.2.3.0.
> Reference Manual updates - J2EE Compliance: Java Transaction API an
[ http://issues.apache.org/jira/browse/DERBY-1933?page=all ]
Rick Hillegas updated DERBY-1933:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Reassigning to 10.2.3.0.
> Reference Manual updates - Setting attributes for the db connection
[ http://issues.apache.org/jira/browse/DERBY-1946?page=all ]
Rick Hillegas updated DERBY-1946:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Reassigning to 10.2.3.0.
> Internal language transformations - explain why users should rewrit
[ http://issues.apache.org/jira/browse/DERBY-1992?page=all ]
Rick Hillegas updated DERBY-1992:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Reassigning to 10.2.3.0.
> Upgrade to DITA Open Toolkit version 1.3
>
[ http://issues.apache.org/jira/browse/DERBY-2127?page=all ]
Rick Hillegas updated DERBY-2127:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Reassigning to 10.2.3.0.
> Hard coded words in the messages which will not get translated in o
[ http://issues.apache.org/jira/browse/DERBY-2134?page=all ]
Rick Hillegas updated DERBY-2134:
-
Fix Version/s: 10.2.3.0
(was: 10.2.2.0)
Reassigning to 10.2.3.0.
> Add long running System test for Derby
> --
Hi Rajesh,
Thanks for bringing up this topic. I have created a new Derby version in
JIRA, 10.2.3.0. I think we can reassign most of these issues to 10.2.3.0.
Regards,
-Rick
Rajesh Kartha wrote:
Hi,
I noticed in JIRA there are about 87 issues marked for fix in 10.2.2,
Here is a filter to g
Thanks, Andrew. I am doing a sync right now. Will post how the build goes
after that.
thanks,
Mamta
On 12/5/06, Andrew McIntyre <[EMAIL PROTECTED]> wrote:
On 12/5/06, Mamta Satoor <[EMAIL PROTECTED]> wrote:
> ok. I have the fix in my codeline for a long time now, but everytime I
try
> to comp
Julius Stroffek <[EMAIL PROTECTED]> writes:
> Hi Saurabh,
>
>> Correct, at this point the transaction is not committed, this only
>> gets committed by the next select statement.
> Not only select statement but any other statement... ;-)
>> Well the writeLocalRollback_() method calls buildRDBRLLBCK
[ http://issues.apache.org/jira/browse/DERBY-2146?page=all ]
Tomohito Nakayama updated DERBY-2146:
-
Attachment: DERBY-2146_2.patch
DERBY-2146_2.status
* Description of the patch
* Add Japanese translated "Getting Started with Derby
Knut Anders Hatlen wrote:
Mike Matrigali <[EMAIL PROTECTED]> writes:
One approach would be to continue to support the latching in the
lockmanager, but to provide an alternate implementation using the
same interfaces (or new interfaces if necessary). Then make the
default module implementati
Hi Saurabh,
Correct, at this point the transaction is not committed, this only
gets committed by the next select statement.
Not only select statement but any other statement... ;-)
Well the writeLocalRollback_() method calls buildRDBRLLBCK() and sends
RDBRLLBCK code-point. I am not sure that t
[ http://issues.apache.org/jira/browse/DERBY-2147?page=all ]
Bernt M. Johnsen updated DERBY-2147:
Derby Info: [Patch Available]
> LIKE predicate does not accept a pure column reference as righthand operand
> (gives ERROR 42824)
> ---
[ http://issues.apache.org/jira/browse/DERBY-2147?page=all ]
Bernt M. Johnsen updated DERBY-2147:
Attachment: DERBY-2147.diff
DERBY-2147.stat
Removed the two tests that disables this functionality.
Updated master for lang/dynamicLikeO
[ http://issues.apache.org/jira/browse/DERBY-1231?page=all ]
Bernt M. Johnsen resolved DERBY-1231.
-
Resolution: Fixed
Committed revision 483042.
> LIKE does not match empty strings when used with a prepared statement
> -
[
http://issues.apache.org/jira/browse/DERBY-2146?page=comments#action_12455973 ]
Tomohito Nakayama commented on DERBY-2146:
--
Thank you Laura :)
I think I could understoodd all of the manual.
If you know improvement on this manual whic
[
http://issues.apache.org/jira/browse/DERBY-1471?page=comments#action_12455972 ]
Tomohito Nakayama commented on DERBY-1471:
--
I will wait for days and will commit the patch ...
> Implement layer B streaming for new methods defined in JD
Hi,
I'm a developer in the Apache Jackrabbit project and in the process of
making it clusterable we're facing some serious problem: we have all
nodes in the cluster share the repository data and are using derby as
database back end, running standalone. When retrieving large binary
data through th
[
http://issues.apache.org/jira/browse/DERBY-2147?page=comments#action_12455954 ]
Bernt M. Johnsen commented on DERBY-2147:
-
The same applies to the escape character which is caught by:
// escape cannot be a column
[ http://issues.apache.org/jira/browse/DERBY-2147?page=all ]
Bernt M. Johnsen reassigned DERBY-2147:
---
Assignee: Bernt M. Johnsen
> LIKE predicate does not accept a pure column reference as righthand operand
> (gives ERROR 42824)
>
[ http://issues.apache.org/jira/browse/DERBY-1231?page=all ]
Bernt M. Johnsen reopened DERBY-1231:
-
Merge to 10.2
> LIKE does not match empty strings when used with a prepared statement
>
[ http://issues.apache.org/jira/browse/DERBY-1231?page=all ]
Bernt M. Johnsen resolved DERBY-1231.
-
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Committed revision 482983.
> LIKE does not match empt
[ http://issues.apache.org/jira/browse/DERBY-1231?page=all ]
Bernt M. Johnsen updated DERBY-1231:
Attachment: DERBY-1231-v3.diff
Thanks Knut. Here's the final patch
> LIKE does not match empty strings when used with a prepared statement
> --
[
http://issues.apache.org/jira/browse/DERBY-1231?page=comments#action_12455934 ]
Knut Anders Hatlen commented on DERBY-1231:
---
Looks good, +1 to commit. You could also remove "NOTE: This may be null if the
pattern is an empty string."
[
http://issues.apache.org/jira/browse/DERBY-1434?page=comments#action_12455931 ]
Knut Anders Hatlen commented on DERBY-1434:
---
This fix cannot be merged to 10.2 automatically because it depends on some
changes to the JUnit framework th
[ http://issues.apache.org/jira/browse/DERBY-2155?page=all ]
Knut Anders Hatlen resolved DERBY-2155.
---
Fix Version/s: 10.3.0.0
Resolution: Fixed
Committed revision 482972.
> checkDataSource and checkDataSource30 fail in the tinderbox test
>
[ http://issues.apache.org/jira/browse/DERBY-2155?page=all ]
Knut Anders Hatlen updated DERBY-2155:
--
Attachment: derby-2155.diff
derby-2155.stat
The attached patch updates the master files so that the tests run cleanly. It
also fixe
[ http://issues.apache.org/jira/browse/DERBY-2155?page=all ]
Knut Anders Hatlen reassigned DERBY-2155:
-
Assignee: Knut Anders Hatlen
> checkDataSource and checkDataSource30 fail in the tinderbox test
>
checkDataSource and checkDataSource30 fail in the tinderbox test
Key: DERBY-2155
URL: http://issues.apache.org/jira/browse/DERBY-2155
Project: Derby
Issue Type: Bug
C
[ http://issues.apache.org/jira/browse/DERBY-1231?page=all ]
Bernt M. Johnsen updated DERBY-1231:
Attachment: DERBY-1231-v2.diff
New version. Ready for commit.
> LIKE does not match empty strings when used with a prepared statement
> ---
101 - 140 of 140 matches
Mail list logo