[ http://issues.apache.org/jira/browse/DERBY-1374?page=all ]
Andreas Korneliussen resolved DERBY-1374:
-
Resolution: Fixed
Committed revision 415557.
compatibility test fails with 'PROTOCOL Data Stream Syntax Error'
[Auto-generated mail]
*Derby* 415379/2006-06-19 19:46:09 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
NANANA NASunOS-5.10_i86pc-i386
Details in
Hi Rick,
Thanks for the feedback. I agree that most of the differences can be
handled using a sed script. The main reason for sending the first email
was that with the client driver running with JDK 1.6 it seems like we
are no longer getting the trailing SQLSTATE information written out by
[
http://issues.apache.org/jira/browse/DERBY-1183?page=comments#action_12416892 ]
Knut Anders Hatlen commented on DERBY-1183:
---
Dag, I see two failures in derbyall with this patch. From
lang/updatableResultSet.java I got a diff that was thousands
[
http://issues.apache.org/jira/browse/DERBY-1108?page=comments#action_12416921 ]
A B commented on DERBY-1108:
3) The test is not ok.
To test what it wants to test, that we can't change the isolation in the
middle of retrieving results on a
held cursor,
Kathey Marsden wrote:
I'll analyze some usage scenarios that I am aware of and see what the
impact might be. The most important thing is that this be a
deliberate choice and that we not rush new functionality and
introduce a regression where there is a reasonable technical
alternative,
Yes for some reason there is a missing newline in the patch I submitted :( Do you want to edit the subquery.out file yourself or should I attach another patch? Do you want the entire patch or just subquery.diff?
On 6/20/06, Rick Hillegas (JIRA) derby-dev@db.apache.org wrote:
[
Olav Sandstaa wrote:
Kathey Marsden wrote:
3) If derby booted at the first connection or the first instantiation
of the driver (whichever came first) , would that solve the
derby.drda.startNetworkServer problem.
This depends on what you mean by the first instantiation of the
driver.
[ http://issues.apache.org/jira/browse/DERBY-1420?page=all ]
Kathey Marsden updated DERBY-1420:
--
Derby Info: (was: [Patch Available])
committed to the trunk
Date: Sun Jun 18 06:39:51 2006
New Revision: 415135
URL:
Hi Brent,
Thanks for the extra information. And thanks to Army for the pointers to
extra documentation. Hopefully our optimizer guru, Jeff Lichtman, will
join the discussion, but he may be on vacation. Please bear with me as I
try to understand your approach. I am going to use some shorthand
Rick Hillegas wrote:
Hi Brent,
...
Plan 3:
Join
/ \
Union TableScan
/ \
IndexScan IndexScan
Each IndexScan would probe for a single key value. If you could just get
the Opimizer to consider this plan, then
Rick Hillegas wrote:
1) Remove the JDBC4-driver-autoloading. This removes a useful
ease-of-development feature and makes us fail to be JDBC4-compliant.
2) Don't boot the engine when registering the embedded driver. Instead,
boot the engine the first time that someone requests an embedded
Thanks, Manish. I can add the new canon myself. I just want to make sure
that you've seen and understood this diff and don't regard it as a
regression.
Regards,
-Rick
Manish Khettry wrote:
Yes for some reason there is a missing newline in the patch I
submitted :(
Do you want to edit the
Hi Mike,
Right.Your proposal is what I had in mind when I was talking about
nextKey. Like you, I would imagine beefing up the existing node that
scans indexes. This solution does give rise to a smaller tree that's
easier to understand. I think it's a little more complicated than the
Rick Hillegas and Kathey Marsden wrote:
[lots of stuff about implementation details that probably should wait a bit]
I think Dan's summary and focus on goals was good:
Dan said ...
I think the goal should be to support auto-loading and to ensure
applications that perform some setup and then
Kathey Marsden wrote:
Rick Hillegas and Kathey Marsden wrote:
[lots of stuff about implementation details that probably should wait
a bit]
I think Dan's summary and focus on goals was good:
Dan said ...
I think the goal should be to support auto-loading and to ensure
applications that
[
http://issues.apache.org/jira/browse/DERBY-1431?page=comments#action_12416986 ]
Andrew McIntyre commented on DERBY-1431:
The -bin distribution in 10.2 currently does build with a demo/programs
directory. With the addition of toursdb to
[
http://issues.apache.org/jira/browse/DERBY-1428?page=comments#action_12416987 ]
Daniel John Debrunner commented on DERBY-1428:
--
Is this a bug? - Derby is behaving as desgined.
Generating derby properties on the fly can lead to
[
http://issues.apache.org/jira/browse/DERBY-1428?page=comments#action_12416995 ]
Rick Hillegas commented on DERBY-1428:
--
I think this behavior is very puzzling to the system administrator, the
end-user, and tech support. What happens if a system
derbynetmats/NSinSameJVM.java fails to run due to Warning
UnknkownHostException: dynxx on Linux with DHCP generated hostname
Key: DERBY-1432
URL:
Andrew McIntyre commented on DERBY-1431:
The -bin distribution in 10.2 currently does build with a demo/programs
directory.
With the addition of toursdb to demo/databases, I've moved the demo programs
into demo/programs. I only did so because that
Dag H. Wanvik commented on DERBY-1338:
--
I did consider including a longer comment - I agree it is better. The
comment is fine, except it should be DRDAProtocolExceptionInfo in all
cases, not plain DRDAProtocolException.
Thanks for reviewing the comment.
David Van Couvering wrote:
I think the issue of derby.system.home and two databases running in the
same VM is a symptom of a wider problem where I am not convinced we
actually work running two instances in the same VM. Derby makes use of
a lot of system properties; if you have two instances,
[
http://issues.apache.org/jira/browse/DERBY-1394?page=comments#action_12417002 ]
Stan Bradbury commented on DERBY-1394:
--
These changes look great. The section reads very smoothly. Thanks again for
the good work. I didn't apply these changes to my
[
http://issues.apache.org/jira/browse/DERBY-1431?page=comments#action_12417004 ]
Stan Bradbury commented on DERBY-1431:
--
I like to plan for success. To me that means, in this case, many more demo
programs, databases, etc. in the this directory.
[ http://issues.apache.org/jira/browse/DERBY-1420?page=all ]
Mamta A. Satoor updated DERBY-1420:
---
Derby Info: [Patch Available]
Make JitTest.java independent of Derby release
--
Key: DERBY-1420
Stan Bradbury (JIRA) wrote:
[
http://issues.apache.org/jira/browse/DERBY-1431?page=comments#action_12417004 ]
Stan Bradbury commented on DERBY-1431:
--
... cast my vote for organizing/grouping files in a hierarchy under the demo
folder.
Hi Stan,
Mike Matrigali wrote:
I would like to see the fix for DERBY-1392 included in the 10.1.3
release if there is a second release candidate. While the bug
is an edge error case, the result is a corrupt db. I believe
there is little risk as again the path is not one usually taken.
The change has
28 matches
Mail list logo
