Identity column can be created with wrong and very large start with value with
J2RE 1.5.0 IBM Windows 32 build pwi32dev-20060412 (SR2) with JIT on
[
http://issues.apache.org/jira/browse/DERBY-1325?page=comments#action_12411899 ]
Mamta A. Satoor commented on DERBY-1325:
Deepa, the patch looks good to me too. I think this bug is result of
Derby-421(worked by me) where I missed cleaning up the
[
http://issues.apache.org/jira/browse/DERBY-1327?page=comments#action_12411900 ]
Kathey Marsden commented on DERBY-1327:
---
I am trying to narrrow down what java calls may be causing this issue.
Because it only reproduces with JIT on I can't really
[ http://issues.apache.org/jira/browse/DERBY-1087?page=all ]
Fernanda Pizzorno closed DERBY-1087:
Updatable result sets behave different depending on the type of query used to
generate the result set
[ http://issues.apache.org/jira/browse/DERBY-1324?page=all ]
Andrew McIntyre reassigned DERBY-1324:
--
Assign To: Andrew McIntyre
Need to remove old copyright notice
---
Key: DERBY-1324
URL:
[ http://issues.apache.org/jira/browse/DERBY-1324?page=all ]
Andrew McIntyre updated DERBY-1324:
---
Fix Version: 10.0.2.2
Need to remove old copyright notice
---
Key: DERBY-1324
URL:
[ http://issues.apache.org/jira/browse/DERBY-1324?page=all ]
Andrew McIntyre updated DERBY-1324:
---
Attachment: derby-1324.diff
Attaching a patch to resolve the noted issues. A search for similar issues did
not turn up any further problems. All of
[ http://issues.apache.org/jira/browse/DERBY-800?page=all ]
Bernt M. Johnsen reopened DERBY-800:
Merging to 10.1-branch
derbylang/ConcurrentImplicitCreateSchema.java fails intermittently with a
lock timeout
[
http://issues.apache.org/jira/browse/DERBY-883?page=comments#action_12411920 ]
Lluis Turro commented on DERBY-883:
---
Manish, it would be great supporting positional parameters. So I vote for both
;-)
Duplicates in group by clause make no sense, is an
[
http://issues.apache.org/jira/browse/DERBY-883?page=comments#action_12411924 ]
Lluis Turro commented on DERBY-883:
---
About question 2. Results would not change but would be a shortcut. If you ask
me I would tell you that reads better 'group by x'.
[Auto-generated mail]
*Derby* 406692/2006-05-15 19:46:07 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
130696566 0 103.53% SunOS-5.10_i86pc-i386
Details in
[ http://issues.apache.org/jira/browse/DERBY-800?page=all ]
Bernt M. Johnsen closed DERBY-800:
--
Fix Version: 10.2.0.0
10.1.3.0
Resolution: Fixed
Committed revision 406881 on 10.1 branch
[
http://issues.apache.org/jira/browse/DERBY-1323?page=comments#action_12411942 ]
Fernanda Pizzorno commented on DERBY-1323:
--
Review:
The patch looks good. I just have a couple of questions.
1.
Implementing the free methods in the Clob and Blob interface
Key: DERBY-1328
URL: http://issues.apache.org/jira/browse/DERBY-1328
Project: Derby
Type: New Feature
Components: JDBC
Reporter:
[ http://issues.apache.org/jira/browse/DERBY-1328?page=all ]
V.Narayanan reassigned DERBY-1328:
--
Assign To: V.Narayanan
Implementing the free methods in the Clob and Blob interface
[ http://issues.apache.org/jira/browse/DERBY-1328?page=all ]
V.Narayanan updated DERBY-1328:
---
Attachment: ClobBlob_free_v1.diff
ClobBlob_free_v1.stat
Implementation of free() methods in Clob and Blob interface
Involves freeing the
[
http://issues.apache.org/jira/browse/DERBY-1303?page=comments#action_12411951 ]
Tomohito Nakayama commented on DERBY-1303:
--
Committed the patch.
Deleting
[
http://issues.apache.org/jira/browse/DERBY-1291?page=comments#action_12411986 ]
Rick Hillegas commented on DERBY-1291:
--
I am getting enough pushback on this refactoring that I believe we should not
commit this patch. We should also back out
[ http://issues.apache.org/jira/browse/DERBY-1322?page=all ]
Fernanda Pizzorno updated DERBY-1322:
-
Attachment: derby-1322.diff
derby-1322.stat
Changes in patch derby-1322.diff:
java/client/org/apache/derby/client/am/ResultSet.java
[ http://issues.apache.org/jira/browse/DERBY-463?page=all ]
Deepa Remesh updated DERBY-463:
---
Attachment: derby-463-v10.1.diff
derby-463-v10.1.status
Attaching 'derby-463-v10.1.diff' which ports this fix to 10.1 branch. This port
is
[ http://issues.apache.org/jira/browse/DERBY-683?page=all ]
Deepa Remesh updated DERBY-683:
---
Fix Version: 10.1.3.0
Derby Info: [Patch Available]
To merge this fix, I have also ported the fix for DERBY-463 which is in the
same area. The patch for
Derby might have more than one cache manager pretty soon, and as I've
been reading source code I've pondered how new cache managers should be
wired into Derby. If we don't change any existing interfaces only one
cache manager will be used, and it will be chosen at Derby boot time.
I'm thinking it
Hello,
I'm posting several questions about Perf tuning. I'd be grateful if people can provide me with answers.
I'm using Derby as an Embedded Database for a prototype application, where Derby is used to run queries on a small set of Rows, very frequently. Rows are inserted into the Tables at
[
http://issues.apache.org/jira/browse/DERBY-655?page=comments#action_12412003 ]
Mamta A. Satoor commented on DERBY-655:
---
I was able to reduce the test case provided to following set of sql which will
reproduce the erroneous behavior in Derby 10.0.
ASSERT failure/IndexOutOfBoundsException with correlated subquery for UPDATE
... SET ... WHERE CURRENT OF ... statement.
Key: DERBY-1329
URL:
[ http://issues.apache.org/jira/browse/DERBY-1245?page=all ]
Anders Morken updated DERBY-1245:
-
Derby Info: [Patch Available]
Add o.a.derby.client.am.ClobWriter test coverage
Key: DERBY-1245
To all of the members here, I want to wish you good luck and success
on the Derby project.
For external reasons, I will not participate in the Derby development process.
My ideas and those of others here should be implemented since I
believe it's a major win for the project itself, however I
[
http://issues.apache.org/jira/browse/DERBY-1329?page=comments#action_12412032 ]
A B commented on DERBY-1329:
Just a note that it's also possible to reproduce this error using ij. The
following ij commands do the same thing as the attached Java program:
Rodrigo Madera wrote:
To all of the members here, I want to wish you good luck and success
on the Derby project.
For external reasons, I will not participate in the Derby development
process.
Thanks for the update Rodrigo. Sometimes I find myself saying, I
wonder what happened to ...
I
[ http://issues.apache.org/jira/browse/DERBY-1303?page=all ]
Tomohito Nakayama resolved DERBY-1303:
--
Resolution: Fixed
The test of derbynet/SuicideOfStreaming.java is failed when programs are
build as Insane.
On 5/10/06, Rick Hillegas [EMAIL PROTECTED] wrote:
This issue is covered by the umbrella DERBY-955 jira. The problem has
been analyzed this far: The tests run cleanly against the classtree but
fail because of permissions exceptions when run against jar files. We
suspect an asymmetry in the
[
http://issues.apache.org/jira/browse/DERBY-1328?page=comments#action_12412080 ]
Rick Hillegas commented on DERBY-1328:
--
Looks good. JDBC4 tests run cleanly. Derbyall runs cleanly except for wisconsin
noise. I can't commit this patch because
Knut Anders observes the following:
This happened when Ole went from b78 to b81, so it might be a Mustang
issue. Ole, how did your re-run with b78 go?
I continue to get clean derbyall runs against the classtree in 1.6.
However, I'm seeing the following permissions exception in the first
nist
Hi,
It appears that you have made the appropriate change.
XADataSource is not a user API, and in fact isn't a kind-of
DataSource. It was misnamed (IMHO) from the beginning. An
XADataSource is a factory that produces XAConnections, which are not
Connections, but are chimeras (produced by
Hi Andrew,
Could there be some extra magic which
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease should document?
When I follow the steps in (2), I get an error. Here are the steps:
587 ant clobber
588 ls
589 rm -rf jars
590 rm -rf javadoc
591 rm -rf snapshot
592 ls
593
35 matches
Mail list logo