[
http://issues.apache.org/jira/browse/DERBY-1045?page=comments#action_12367912 ]
Knut Anders Hatlen commented on DERBY-1045:
---
You are not testing version 10.1 of the client driver, but version
10.2 against master files from the 10.1 branch.
Deepa Remesh [EMAIL PROTECTED] writes:
On 2/24/06, Knut Anders Hatlen [EMAIL PROTECTED] wrote:
You might also consider getting rid of pkgcnstkn, pkgid and pkgsn
since they are stored in pkgnamcsn anyway. If you remove them, we only
have two variables that aren't reset like the others.
It
[Auto-generated mail]
*Derby* 381135/2006-02-26 19:45:39 CET
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
3637634 0 100.10% CYGWIN_NT-5.1_i686-unknown
NA NA NANA
[
http://issues.apache.org/jira/browse/DERBY-690?page=comments#action_12367925 ]
Andreas Korneliussen commented on DERBY-690:
Dan wrote:
My thought here is that the updated row in the ResultSet would then
reflect a state of the database that
[
http://issues.apache.org/jira/browse/DERBY-788?page=comments#action_12367926 ]
Knut Anders Hatlen commented on DERBY-788:
--
I'm planning to review and commit this patch.
'store/encryptionKey.sql' fails on Solaris 10
[
http://issues.apache.org/jira/browse/DERBY-690?page=comments#action_12367929 ]
Fernanda Pizzorno commented on DERBY-690:
-
Daniel wrote:
___
This also seems closely tied to implementing the ResultSet.refreshRow() method,
if we continue with
[ http://issues.apache.org/jira/browse/DERBY-809?page=all ]
Kristian Waagan updated DERBY-809:
--
Attachment: DERBY-809-1b-javadoc.stat
DERBY-809-1b-javadoc.diff
Yes, we need to remove references to disconnections here as well. Thanks for
[ http://issues.apache.org/jira/browse/DERBY-809?page=all ]
Kristian Waagan updated DERBY-809:
--
Attachment: (was: DERBY-809-1a-javadoc.diff)
Incorrect documentation for 'NetworkServerControl.logConnections(boolean)'
[ http://issues.apache.org/jira/browse/DERBY-809?page=all ]
Kristian Waagan updated DERBY-809:
--
Attachment: (was: DERBY-809-1a-javadoc.stat)
Incorrect documentation for 'NetworkServerControl.logConnections(boolean)'
[ http://issues.apache.org/jira/browse/DERBY-1058?page=all ]
Andreas Korneliussen updated DERBY-1058:
Attachment: HoldabilityIssue.java
The attached program can be used to reproduce this issue
derby fails supporting holdable scrollable
Mike Matrigali wrote:
I was not aware of the alter table dependency check for offline
compress, this must be outside of store somehow - maybe something
tied to all alter table statements. It may make sense
to change online compress to hook up with whatever offline compress
is doing to make
[ http://issues.apache.org/jira/browse/DERBY-953?page=all ]
Kristian Waagan reassigned DERBY-953:
-
Assign To: Kristian Waagan
Add miscellaneous Statement methods introduced by JDBC 4
Mike Matrigali wrote:
I was not aware of the alter table dependency check for offline
compress, this must be outside of store somehow - maybe something
tied to all alter table statements. It may make sense
to change online compress to hook up with whatever offline compress
is doing to make
[ http://issues.apache.org/jira/browse/DERBY-788?page=all ]
Knut Anders Hatlen resolved DERBY-788:
--
Resolution: Fixed
Assign To: Kristian Waagan
Patch looks good. store/encryptionKey.sql does not fail under
Solaris 10 / Sun JVM 1.5.0.
call to stored procedure with out params fails in embedded driver
-
Key: DERBY-1059
URL: http://issues.apache.org/jira/browse/DERBY-1059
Project: Derby
Type: Sub-task
Components: JDBC
Versions:
Hello,
Some time ago I created DERBY-753
(http://issues.apache.org/jira/browse/DERBY-753), but there has not been
any activity on it since then. It says that the links in the table of
contents of the HTML book manuals do not work.
Can anyone confirm that the problem (still) exists?
ResultSet methods should throw exception when the ResultSet is closed
-
Key: DERBY-1060
URL: http://issues.apache.org/jira/browse/DERBY-1060
Project: Derby
Type: Bug
Components: JDBC, Network
[Auto-generated mail]
*TinderBox_Derby* 381300/2006-02-27 10:22:24 CET
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
2637635 0 102.00% SunOS-5.10_i86pc-i386
Details in
Knut Anders Hatlen wrote:
Lance J. Andersen [EMAIL PROTECTED] writes:
We clarified this in JDBC 4 spec
Once a ResultSet has been closed, any attempt to access any of its
methods with
the exception of the isClosed method will result in a SQLException being
thrown. ResultSetMetaData instances
Kathey Marsden wrote:
Manjula G Kutty wrote:
I have closed all the statements, prepared statements and resultsets
in the largeCodeGen.java file. But still the test passes with embedded
but fails with derbyClient. I'm attaching the modified
largeCodeGen.java file
Hi Manjula,
Because this
Kristian Waagan wrote:
Hello,
Some time ago I created DERBY-753
(http://issues.apache.org/jira/browse/DERBY-753), but there has not been
any activity on it since then. It says that the links in the table of
contents of the HTML book manuals do not work.
Can anyone confirm that the problem
[
http://issues.apache.org/jira/browse/DERBY-925?page=comments#action_12367959 ]
Dyre Tjeldvoll commented on DERBY-925:
--
I have some questions about the columns in the resultset that is returned from
this method.
Abbreviations:
John Embretsen wrote:
Kristian Waagan wrote:
Hello,
Some time ago I created DERBY-753
(http://issues.apache.org/jira/browse/DERBY-753), but there has not
been any activity on it since then. It says that the links in the
table of contents of the HTML book manuals do not work.
Can anyone
[
http://issues.apache.org/jira/browse/DERBY-690?page=comments#action_12367960 ]
Dag H. Wanvik commented on DERBY-690:
-
I checked how the trigger situation is handled in Oracle, since they
do support Scrollable updatable insensitive result sets. In
Mike Matrigali wrote:
The SUR should not know anything about the underlying implementation
of the access method getting the row, so having it read a timestamp
from page does not work. If the timestamp is not in the rowlocation,
we could add a get a timestamp for row at this rowlocation, but
[
http://issues.apache.org/jira/browse/DERBY-965?page=comments#action_12367962 ]
Dag H. Wanvik commented on DERBY-965:
-
Thanks for looking at this Bryan.
Bryan wrote:
It would be nice to have comments in metadata_net.properties
explaining the
[
http://issues.apache.org/jira/browse/DERBY-965?page=comments#action_12367964 ]
Dag H. Wanvik commented on DERBY-965:
-
Kathey wrote:
Your earlier comment said: Note that this raises an upgrade issue, in
that the existing client would crash if the
[
http://issues.apache.org/jira/browse/DERBY-690?page=comments#action_12367965 ]
Daniel John Debrunner commented on DERBY-690:
-
Andreas wrote:
A transaction can always see its own uncommitted changes in the database, so
it does not
conflict
Fernanda Pizzorno (JIRA) wrote:
[
http://issues.apache.org/jira/browse/DERBY-690?page=comments#action_12367929
]
Fernanda Pizzorno commented on DERBY-690:
-
Daniel wrote:
___
This also seems closely tied to implementing the
I have tried to ping Scott privately on the email address linked to his
name: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]. The mail was
undeliverable. At the risk of incurring my peers' censure, I will page
him in the subject line of an email message. I do think this is an
important enhancement
[ http://issues.apache.org/jira/browse/DERBY-396?page=all ]
Rick Hillegas updated DERBY-396:
Priority: Major (was: Critical)
Downgrading priority to major.
Support for ALTER STATEMENT to DROP , MODIFY, RENAME a COLUMN
halooothey say that VACUUM, for instance, is a unique command 2 PostGreSQL, and each RDBMS has its own unique features too, which r not listed within the SQL standards...Okay, wot r those features unique to derby?any help or point out is greatly appreciatedrgrds
Telefonieren Sie ohne weitere
Hi Scott,
Please forgive me for putting you on the spot by paging you in the
subject line of this message. I have tried to privately ping your JIRA
email address ([EMAIL PROTECTED] mailto:[EMAIL PROTECTED]), but the
mail bounced back.
You graciously volunteered to work on DERBY-396. The
I've been hearing from quite a few people and just wanted to let
everyone know that infrastructure is still working on isolating the
cause. If you're interested in details, see
http://issues.apache.org/jira/browse/INFRA-697
-jean
I don't know off hand, but you should note that log record
size is most dependent on the size of the data that is affected.
For instance an insert log record will have the part of the row
on that page in that log record.
Raymond Raymond wrote:
Hi, anyone knows how long is a log records in
[
http://issues.apache.org/jira/browse/DERBY-809?page=comments#action_12367977 ]
Bryan Pendleton commented on DERBY-809:
---
Patch DERBY-809-1b-javadoc.diff submitted as revision 381375
http://svn.apache.org/viewcvs?rev=381375view=rev
Note that this is
[ http://issues.apache.org/jira/browse/DERBY-855?page=all ]
Jean T. Anderson closed DERBY-855:
--
no problems with patch applied reported, so closing.
Document optimizer overrides which were introduced in 10.2
[ http://issues.apache.org/jira/browse/DERBY-608?page=all ]
Jean T. Anderson closed DERBY-608:
--
No problems have been reported with the patch that was committed, so closing.
Documentation will require changes once dynamic parameters are supported
Andreas Korneliussen wrote:
Mike Matrigali wrote:
I was not aware of the alter table dependency check for offline
compress, this must be outside of store somehow - maybe something
tied to all alter table statements. It may make sense
to change online compress to hook up with whatever
[ http://issues.apache.org/jira/browse/DERBY-570?page=all ]
Jean T. Anderson closed DERBY-570:
--
No problems have been reported with the patch that was committed, so closing.
wrong java.sql.Type id implied for LONG VARCHAR FOR BIT DATA
[ http://issues.apache.org/jira/browse/DERBY-761?page=all ]
Jean T. Anderson closed DERBY-761:
--
No problems have been reported with the committed patch, so closing.
The reserved words list in the reference manual doesn't look uptodate
[ http://issues.apache.org/jira/browse/DERBY-869?page=all ]
Jean T. Anderson closed DERBY-869:
--
No problems have been reported with the committed patch, so closing.
documentation to address Derby-783
--
[ http://issues.apache.org/jira/browse/DERBY-678?page=all ]
Jean T. Anderson closed DERBY-678:
--
No problems have been reported with the committed patch, so closing.
derby documentation does not reflect changes to update lock behavior
[ http://issues.apache.org/jira/browse/DERBY-668?page=all ]
Kathey Marsden updated DERBY-668:
-
Priority: Critical (was: Minor)
I am changing this to Critical as its impact is apparent even when users are
just using classpath and derby automatically
[ http://issues.apache.org/jira/browse/DERBY-76?page=all ]
Jean T. Anderson closed DERBY-76:
-
Fix Version: 10.1.2.3
Resolution: Fixed
Verified fixed in 10.1 documentation set.
Stored procedure cannot be invoked with VALUES statement
Andreas Korneliussen wrote:
Mike Matrigali wrote:
The SUR should not know anything about the underlying implementation
of the access method getting the row, so having it read a timestamp
from page does not work. If the timestamp is not in the rowlocation,
we could add a get a timestamp for
Daniel John Debrunner [EMAIL PROTECTED] writes:
Fernanda wrote:
I do not think implementing the ResultSet.refreshRow()
method would help in this case. We are implementing result sets of
type TYPE_SCROLL_INSENSITIVE and according to the JBDC API
Tutorial and Reference, Third Edition p.759,
[
http://issues.apache.org/jira/browse/DERBY-956?page=comments#action_12367988 ]
Rajesh Kartha commented on DERBY-956:
-
I tried the encryptionAll suite multiple times with latest v10.1 jars and this
issue is not seen on any of the above OSes. It is
Thanks Bryan for reading my patch. Please see my answers below:
On 2/26/06, Bryan Pendleton [EMAIL PROTECTED] wrote:
Three small comments:
1) It wasn't clear to me why these needed to be applied as two
separate patches. I would be comfortable putting the test and the
fix in the same commit;
SqlException while fetching message results in recursive calls between
SqlException.getSQLException and Sqlca.getJDBCMessage
Key: DERBY-1061
URL:
[
http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12367992 ]
Anurag Shekhar commented on DERBY-1061:
---
runnning test case jdbcapi/connectionJdbc20.java exposes this bug
SqlException while fetching message results in recursive
[
http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12367994 ]
Anurag Shekhar commented on DERBY-1061:
---
I didn't notice that SqlException doesn't extends from SQLException.
How about creating a SQLException in Sqlca itself with out
[
http://issues.apache.org/jira/browse/DERBY-809?page=comments#action_12367995 ]
Kristian Waagan commented on DERBY-809:
---
I reviewed Jeff's patch (derby809.diff), and it looks good. I do have two
comments:
1) The DOCTYPE tags have been changed, but
[ http://issues.apache.org/jira/browse/DERBY-1061?page=all ]
Anurag Shekhar updated DERBY-1061:
--
Summary: while fetching message results in recursive calls between
SqlException.getSQLException and Sqlca.getJDBCMessage (was: SqlException while
[ http://issues.apache.org/jira/browse/DERBY-1061?page=all ]
Anurag Shekhar updated DERBY-1061:
--
Summary: SqlException while fetching message results in recursive calls
between SqlException.getSQLException and Sqlca.getJDBCMessage (was: while
Thanks Kristian,
We usually do an edit before any release, and
capitalization consistency gets picked up then. So I
think we should commit it.
Thanks again!
--- Kristian Waagan (JIRA) derby-dev@db.apache.org
wrote:
[
I can tell you that this is a problem that could be
hard to fix. The single-html books are not a normal
result of the DITA transform. However, some time ago
Andrew found an xsl file on the web that we were able
to use to transform the half-processed PDF transforms
from the DITA process and
[ http://issues.apache.org/jira/browse/DERBY-1002?page=all ]
Deepa Remesh updated DERBY-1002:
Attachment: (was: derby1002-patch2-v1.diff)
Check that DRDAStatement and DRDAResultSet states are reset when they are
re-used
[ http://issues.apache.org/jira/browse/DERBY-1002?page=all ]
Deepa Remesh updated DERBY-1002:
Attachment: (was: derby1002-patch2-v1.status)
Check that DRDAStatement and DRDAResultSet states are reset when they are
re-used
[
http://issues.apache.org/jira/browse/DERBY-690?page=comments#action_12367999 ]
Daniel John Debrunner commented on DERBY-690:
-
Andreas wrote:
--- quote
True. This would also be the situation if:
* The ResultSet selects a,b
* Another statement
[Auto-generated mail]
*TinderBox_Derby* 381339/2006-02-27 14:52:42 CET
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1637636 0 102.03% SunOS-5.10_i86pc-i386
Details in
Monday, February 27, 2006, 7:01:25 PM CET, Jeff Levitt wrote:
Thanks Kristian,
We usually do an edit before any release, and
capitalization consistency gets picked up then. So I
think we should commit it.
I'm just curious; who edits what before any release? Are you saying that
you (?) are
[ http://issues.apache.org/jira/browse/DERBY-925?page=all ]
Rick Hillegas updated DERBY-925:
Attachment: TypePrinter.java
Hi Dyre,
As far as CHAR_OCTET_LENGTH is concerned, I think that
DataTypeDescriptor.getTypeId().isStringTypeId() and
Yep! I've done it the last few releases. Its not
that bad really. I do a spell check and look for
consistency and grammar fixes like this. I'm
definitely glad to welcome additional help if someone
wants to contribute!
We also do technical reviews of each manual before
each release. Everyone
Jira seems to be down. I wanted to change the fix versoin to 10.2. I have a customer who ran into this problem and they would like to see this documented in 10.2 release. Jeff, thanks for working on it.
thanks,
Mamta
On 2/7/06, Mamta A. Satoor (JIRA) derby-dev@db.apache.org wrote:
Until Derby-911
Jeff Levitt wrote:
Yep! I've done it the last few releases. Its not
that bad really. I do a spell check and look for
consistency and grammar fixes like this. I'm
definitely glad to welcome additional help if someone
wants to contribute!
We also do technical reviews of each manual
[ http://issues.apache.org/jira/browse/DERBY-1002?page=all ]
Deepa Remesh updated DERBY-1002:
Attachment: derby1002-patch2-v2.diff
derby1002-patch2-v2.status
Attaching 'derby1002-patch2-v2.diff' for Bryans' comments in the following
[
http://issues.apache.org/jira/browse/DERBY-1056?page=comments#action_12368009 ]
Daniel John Debrunner commented on DERBY-1056:
--
Just to be clear, I wasn't suggesting that security issues related to localhost
be removed from this bug. I was
Joe wrote:
halooo
they say that VACUUM, for instance, is a unique command 2 PostGreSQL, and
each RDBMS has its own unique features too, which r not listed within the SQL
standards...
Okay, wot r those features unique to derby?
any help or point out is greatly appreciated
rgrds
Hi, Joe,
On 2/27/06, Kathey Marsden [EMAIL PROTECTED] wrote:
derbytools.jar will automatically put derbyclient.jar in the
classpath. Since you have derbytools.jar from trunk before
derbyclient.jar version 10.1 in your classpath, derbyclient.jar will
be shadowed. Sysinfo will however report that you
Are there any initial thoughts to require authentication for databases
that are accessible through network server, outside of localhost? While
this would change default behavior of network server, with more work
being done in authentication and authorization areas, should Derby
start planning
[
http://issues.apache.org/jira/browse/DERBY-1056?page=comments#action_12368012 ]
Kathey Marsden commented on DERBY-1056:
---
That sounds good as at least that would be a clear issue. I think also as
you say it would be good to explore this scenario
Andrew McIntyre wrote:
I hadn't considered the mixed jar environment, sorry, and I guess
there's no choice but to take out the Class-Path attribute from
derbytools.jar. Sadly, it cripples the spirit of 1019: there is then
no direct path to using the tools and one must explain classpath
before
Andrew McIntyre wrote:
On 2/27/06, Kathey Marsden [EMAIL PROTECTED] wrote:
derbytools.jar will automatically put derbyclient.jar in the
classpath. Since you have derbytools.jar from trunk before
derbyclient.jar version 10.1 in your classpath, derbyclient.jar will
be shadowed. Sysinfo will
[ http://issues.apache.org/jira/browse/DERBY-668?page=all ]
Bryan Pendleton updated DERBY-668:
--
Attachment: sysinfo_Feb27_2006.diff
Here's another version of the patch for review.
The primary difference between this version and the previous
On 2/27/06, Kathey Marsden [EMAIL PROTECTED] wrote:
Andrew McIntyre wrote:
I hadn't considered the mixed jar environment, sorry, and I guess
there's no choice but to take out the Class-Path attribute from
derbytools.jar. Sadly, it cripples the spirit of 1019: there is then
no direct path to
Kathey Marsden wrote:
Andrew McIntyre wrote:
I hadn't considered the mixed jar environment, sorry, and I guess
there's no choice but to take out the Class-Path attribute from
derbytools.jar. Sadly, it cripples the spirit of 1019: there is then
no direct path to using the tools and one must
Andrew McIntyre wrote:
On 2/27/06, Daniel John Debrunner [EMAIL PROTECTED] wrote:
Let's not rush into removing this feature, which is really useful for
the majority of Derby users. Let's understand the impact on existing
users and see what the best way forward is.
Ack! Read this about two
Daniel John Debrunner wrote:
Isn't DERBY-1019 the correct place for this?
Or perhaps a separate issue created to autoload derbyclient.jar with
derbytools.jar.I certainly did not glean that impact from the
DERBY-1019 description. It would be nice to see it as a separate issue.
Rick,
Scott was one of my students, and he was working on DERBY-396. He has since
graduated and moved on from our university. He ran into some problems with DERBY-396,
which can simply be summed up as problems with return values. When you are accessing a
table to alter it, you need to
Well unfortunately, i am afraid your milage is going to vary here.
The tutorial and reference, while informative is not part of the
specification. Some vendors might have used the additional details
when crafting their implementation others might have just followed the
spec. I will raise this
Hi Darcy,
Thanks for this update. I will unassign DERBY-396. I will happily to
mouse into DERBY-396 any information you think is worth forwarding.
Regards,
-Rick
Darcy Benoit wrote:
Rick,
Scott was one of my students, and he was working on DERBY-396. He
has since graduated and moved
[ http://issues.apache.org/jira/browse/DERBY-396?page=all ]
Rick Hillegas reassigned DERBY-396:
---
Assign To: (was: Scott MacDonald)
Support for ALTER STATEMENT to DROP , MODIFY, RENAME a COLUMN
#2 seems best to me, i just didn't know if it fit with the current
derby architecture. I think it also has the benefit of least
amount of extra code in the system for a relative infrequent ddl
operation.
As you point out a move toward sharing the alter code will make it
much more likely no
Change the internal implemetation of SYSCS_INPLACE_COMPRESS_TABLE to share
existing alter table
---
Key: DERBY-1062
URL: http://issues.apache.org/jira/browse/DERBY-1062
Project:
I see this fail on ALL platforms on the current tinderbox and daily test
runs:
http://www.multinet.no/~solberg/public/Apache/TinderBox_Derby/Limited/testSummary-current.html
svn 381405
http://www.multinet.no/~solberg/public/Apache/Derby/Limited/testSummary-current.html
svn 381407
Hi Sunitha,
I went through the patch and it looks good. However, the patch
(testSecMec.java file) does not apply cleanly to the latest trunk
revision. Please upload a new version of the patch and I'll take a
relook.
Minor comments:
1. In testSecMec.java, it would be good to update the comment
[ http://issues.apache.org/jira/browse/DERBY-930?page=all ]
Rick Hillegas updated DERBY-930:
Attachment: ClassloadingTest.jar
I have attached a jarred up experiment which demonstrates a
SecurityManager-induced classloading issue which results in the
Autoloading of JDBC drivers via derbytools.jar manifest Class-Path attribute
Key: DERBY-1063
URL: http://issues.apache.org/jira/browse/DERBY-1063
Project: Derby
Type: Improvement
[ http://issues.apache.org/jira/browse/DERBY-1063?page=all ]
Andrew McIntyre updated DERBY-1063:
---
Attachment: derby1063.diff
Attaching patch which combines reinstituting of derbytools.jar's Class-Path
attribute, along with an improvement to sysinfo's
[ http://issues.apache.org/jira/browse/DERBY-1041?page=all ]
Deepa Remesh resolved DERBY-1041:
-
Resolution: Fixed
Patch committed to 10.1 branch as svn revision 380246
Modify derbynet/testProperties.java test to run with 10.1client/10.2 server
[ http://issues.apache.org/jira/browse/DERBY-1041?page=all ]
Deepa Remesh closed DERBY-1041:
---
Modify derbynet/testProperties.java test to run with 10.1client/10.2 server
---
[ http://issues.apache.org/jira/browse/DERBY-1045?page=all ]
Andrew McIntyre resolved DERBY-1045:
Fix Version: 10.2.0.0
Resolution: Fixed
Assign To: Andrew McIntyre
Related to DERBY-1019. Removed derbytools.jar classpath attribute
[
http://issues.apache.org/jira/browse/DERBY-668?page=comments#action_12368045 ]
Andrew McIntyre commented on DERBY-668:
---
Hi Bryan,
This looks good to me. Dan would need to comment on the security ramifications
of needing the getProtectionDomain
Delete cascade causes NULL values inserted into table when after delete Trigger
fires
-
Key: DERBY-1064
URL: http://issues.apache.org/jira/browse/DERBY-1064
Project: Derby
Type: Bug
Jean T. Anderson wrote:
I've been hearing from quite a few people and just wanted to let
everyone know that infrastructure is still working on isolating the
cause. If you're interested in details, see
http://issues.apache.org/jira/browse/INFRA-697
They believe they found the problem and
Jean T. Anderson wrote:
I've been hearing from quite a few people and just wanted to let
everyone know that infrastructure is still working on isolating the
cause. If you're interested in details, see
http://issues.apache.org/jira/browse/INFRA-697
It looks like they found the problem and came
[ http://issues.apache.org/jira/browse/DERBY-1063?page=all ]
Andrew McIntyre updated DERBY-1063:
---
Attachment: (was: derby1063.diff)
Autoloading of JDBC drivers via derbytools.jar manifest Class-Path attribute
[ http://issues.apache.org/jira/browse/DERBY-1063?page=all ]
Andrew McIntyre updated DERBY-1063:
---
Attachment: derby1063.diff
Autoloading of JDBC drivers via derbytools.jar manifest Class-Path attribute
[
http://issues.apache.org/jira/browse/DERBY-819?page=comments#action_12368049 ]
Rick Hillegas commented on DERBY-819:
-
A couple more comments:
1) TestJDBC40Exception fails when I run the jdbc4 suite. It incurs a
permissions exception.
2) While
1 - 100 of 120 matches
Mail list logo
