[ http://issues.apache.org/jira/browse/DERBY-1463?page=all ]
V.Narayanan updated DERBY-1463:
---
Attachment: JavaDocWarnings.diff
JavaDocWarnings.stat
Please find attached patch for fix.
thanx
Narayanan
Resolve javadoc warnings in
Hi,
As part of Derby SQL Authorization mode, I am looking intocollecting privilege requirements for a new constraint and saving it into SYSDEPENDS using dependency manager. Constraints are unlike views and triggers in the sense thatone can create only single view or trigger with a given sql
Hi,
Thank You for pointing this out. Related to patch for 1445. Have raised
a JIRA issue and attached patch.
thanx
Narayanan
Deepa Remesh wrote On 06/29/06 08:07,:
Noticed following javadoc warnings in trunk:
[javadoc]
[ http://issues.apache.org/jira/browse/DERBY-1463?page=all ]
Knut Anders Hatlen resolved DERBY-1463:
---
Fix Version: 10.2.0.0
Resolution: Fixed
Committed revision 417953.
Resolve javadoc warnings in BrokeredCallableStatement40
[
http://issues.apache.org/jira/browse/DERBY-1463?page=comments#action_12418399 ]
V.Narayanan commented on DERBY-1463:
thanx for the commit knut
Narayanan
Resolve javadoc warnings in BrokeredCallableStatement40
[ http://issues.apache.org/jira/browse/DERBY-937?page=all ]
Andreas Korneliussen updated DERBY-937:
---
Attachment: DERBY-937.diff
DERBY-937.stat
I was able to reproduce this problem on every run on a very fast laptop (it was
not
[ http://issues.apache.org/jira/browse/DERBY-937?page=all ]
Andreas Korneliussen reassigned DERBY-937:
--
Assign To: Andreas Korneliussen
Instability in wisconsin test
-
Key: DERBY-937
URL:
[Auto-generated mail]
*Derby* 417826/2006-06-28 19:46:06 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
2715713 0 105.95% SunOS-5.10_i86pc-i386
Details in
[Auto-generated mail]
*TinderBox_Derby* 417953/2006-06-29 09:03:01 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1675674 2 117.11% SunOS-5.10_i86pc-i386
Details in
I've been looking for some time for a good embedded database that
would work for desktop applications. Derby is ideal for that and I am
starting to use it more and more in various examples and tutorials
that I am writing for Cayenne. But there is one feature that I am
missing in Derby (or
I've been looking for some time for a good embedded database that
would work for desktop applications. Derby is ideal for that and I am
starting to use it more and more in various examples and tutorials
that I am writing for Cayenne. But there is one feature that I am
missing in Derby (or
Hi Andrus!
After you left, we were playing around with the problem and were
thinking along the same lines as your second solution. Some peer-to-peer
protocol or some multicast membership protocol (e.g. something like
JGroups http://www.jgroups.org/javagroupsnew/docs/index.html. I have
done
Cool. I actually started prototyping something similar this morning,
with one difference that I am not defining a master server, but
rather making it peer-to-peer (where the ownership of the database is
transferred on demand between the applications). This will likely
reduce the throughput
Hi David,
Thanks for your comments.
My comments inline
Thanks,
Ramin
On 6/27/06, David Van Couvering [EMAIL PROTECTED] wrote:
Hi, Ramin. Great document! Very nicely done.
Here are my comments:
- You're a UML use case guy. Great! Wish there was more of that in
software design,
Hi Satheesh
Thanks for your commentsI will post the document ddlutils-dev alias
as well.
Thanks,
Ramin
On 6/27/06, Satheesh Bandaram [EMAIL PROTECTED] wrote:
Great document and good comments from David. I think it would be good to
follow ddlUtils approach (approach 2) if feasible. Ramin,
[ http://issues.apache.org/jira/browse/DERBY-1444?page=all ]
Andreas Korneliussen resolved DERBY-1444:
-
Resolution: Fixed
Derby Info: (was: [Patch Available])
Resolving the issue since the patch has been committed to both trunk and
[ http://issues.apache.org/jira/browse/DERBY-1461?page=all ]
Tomohito Nakayama updated DERBY-1461:
-
Attachment: DERBY-1461.patch
Description of the patch :
* The method writeScalarStream was separeted to two methods for encrypted
stream and
[ http://issues.apache.org/jira/browse/DERBY-1351?page=all ]
Fernanda Pizzorno reassigned DERBY-1351:
Assign To: Fernanda Pizzorno
lang/forupdate.sql fails with derbyclient in the 10.1 branch
[
http://issues.apache.org/jira/browse/DERBY-1393?page=comments#action_12418457 ]
Knut Anders Hatlen commented on DERBY-1393:
---
Thanks for the info, Rick! Seems like setObject() with
targetSqlType==JAVA_OBJECT should be supported too, then. For
Andrus Adamchik wrote:
(a) all apps run on the same machine (but in different VMs)
(b) usually only one instance at a time would work with the database,
but other instances can occasionally access the db in the background
(no need to deal with massive concurrency)
The way this is usually
Hello,
When working on EmbedPreparedStatement.java, I noticed that a few
methods synchronize on the connection object, for instance addBatch. The
code typically looks like this:
synchronized (getConnectionSynchronization()) {
// Do stuff
}
The getConnectionSynchronization-method
runtimestatistics can show that an index is being used even when it isn't
--
Key: DERBY-1464
URL: http://issues.apache.org/jira/browse/DERBY-1464
Project: Derby
Type: Bug
Components: SQL
NetworkServerControl.start() should throw an exception and not just print
exceptions starting network server
Key: DERBY-1465
URL:
Kathey Marsden wrote:
The way this is usually accomplished is with embedded server. Network
server is started in the same JVM as the primary instance. The primary
instance accesses with embedded connections. Other JVM's can access
with client.
Yes. But Angus' extra problem as I understand
[ http://issues.apache.org/jira/browse/DERBY-1465?page=all ]
Kathey Marsden updated DERBY-1465:
--
Summary: NetworkServerControl.start() should throw an exception and not
just print exceptions if the server fails to start (was:
+1
We have run a testcycle on 10.1.3.1 with tests as specified below on
platforms as specified below.
We did NOT discover any regressions.
We saw only one new failure, as compared to tests on previous versions:
filed as http://issues.apache.org/jira/browse/DERBY-1430
We do not regard this as
Bernt M. Johnsen wrote:
Yes. But Angus' extra problem as I understand it, is that the apps will
I apologize for spelling Andrus' name wrong. Sorry.
--
Bernt Marius Johnsen, Database Technology Group,
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway
Andrew McIntyre [EMAIL PROTECTED] writes:
Hello derby-dev,
I have posted a new release candidate for 10.1.3 here:
http://people.apache.org/~fuzzylogic/10.1.3.1/
+1 to make 10.1.3.1 an official release.
I have tested the release candidates by running derbyall on the
following platforms:
Network Server should flush the PrintWriter after console output
Key: DERBY-1466
URL: http://issues.apache.org/jira/browse/DERBY-1466
Project: Derby
Type: Improvement
Components: Network Server
It would be useful to have a NetworkServerControl start API that took a
timeout parameter
--
Key: DERBY-1467
URL: http://issues.apache.org/jira/browse/DERBY-1467
Project: Derby
Not a problem :-)
Yeah, I am looking for a solution that would work with a bunch of
independent applications.
Andrus
On Jun 29, 2006, at 2:23 PM, Bernt M. Johnsen wrote:
Bernt M. Johnsen wrote:
Yes. But Angus' extra problem as I understand it, is that the apps
will
I apologize for
+1 to make 10.1.3.1 an official release.
I have manually tested that DERBY-1058 has been fixed.
-- Andreas
[ http://issues.apache.org/jira/browse/DERBY-1351?page=all ]
Fernanda Pizzorno updated DERBY-1351:
-
Attachment: derby-1351.diff
derby-1351.stat
I have run this test several times on Solaris, Linux, and Windows with low
priority and
[ http://issues.apache.org/jira/browse/DERBY-1351?page=all ]
Fernanda Pizzorno updated DERBY-1351:
-
Derby Info: [Patch Available]
lang/forupdate.sql fails with derbyclient in the 10.1 branch
Kathey Marsden wrote:
Andrew McIntyre wrote:
Hello derby-dev,
I have posted a new release candidate for 10.1.3 here:
http://people.apache.org/~fuzzylogic/10.1.3.1/
+1.
No unknown failures found.
I ran the derbyall suite and other tests on the following platforms:
OS:
Red Hat
[
http://issues.apache.org/jira/browse/DERBY-1465?page=comments#action_12418481 ]
John H. Embretsen commented on DERBY-1465:
--
The relationship between the Network Server API and the
derby.drda.startNetworkServer property (and its related
[ http://issues.apache.org/jira/browse/DERBY-822?page=all ]
Kathey Marsden updated DERBY-822:
-
Derby Info: [Existing Application Impact, Release Note Needed] (was:
[Patch Available])
RELEASE NOTE:
Pre-fetching with Network Client/Server is a
Kathey Marsden (JIRA) wrote:
Location where errors occur embedded environment is different.
I guess something went wrong when writing this sentence ...
--
Øystein
Sanket Sharma wrote:
This sounds like a perfect case for JMX soultion and can be added to
list of requirements on derby Wiki. Tracing options (enable/disable)
The requirement for this is that we have something that can be turned on
quickly by the user when talking to tech support so we can
Øystein Grøvlen wrote:
Kathey Marsden (JIRA) wrote:
Location where errors occur embedded environment is different.
Maybe
The location where errors occur in client/server environments is
different than embedded.
?
I had an example of how a user that called executeQuery(), retrieved
Thanks, Ramin, no further comments or issues, I look forward to your
next revision.
David
Ramin Moazeni wrote:
Hi David,
Thanks for your comments.
My comments inline
Thanks,
Ramin
On 6/27/06, David Van Couvering [EMAIL PROTECTED] wrote:
Hi, Ramin. Great document! Very nicely done.
Kristian Waagan wrote:
I think a single connection is not expected to be shared between
multiple threads simultaneously. Maybe the necessary synchronization is
done at a lower level in the system.
This is not intended to be a complete answer, and perhaps I'm
misunderstanding the thrust of
IMHO, this is exactly the kind of thing JMX is suited for.
David
Kathey Marsden wrote:
Sanket Sharma wrote:
This sounds like a perfect case for JMX soultion and can be added to
list of requirements on derby Wiki. Tracing options (enable/disable)
The requirement for this is that we have
Andrew McIntyre wrote:
Hello derby-dev,
I have posted a new release candidate for 10.1.3 here:
http://people.apache.org/~fuzzylogic/10.1.3.1/
+1 for this release.
I have tested the release candidates with some simple performance tests
with 1.4.2 vm on windows and linux and it looks good
Andreas Korneliussen (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-937?page=all ]
Andreas Korneliussen updated DERBY-937:
---
Attachment: DERBY-937.diff
DERBY-937.stat
I was able to reproduce this problem on every run
Andrus Adamchik wrote:
Not a problem :-)
Yeah, I am looking for a solution that would work with a bunch of
independent applications.
Andrus
Just to understand is the reason network server solution is not ok
performance? Or is the problem that you don't want to have to
start a server up
[ http://issues.apache.org/jira/browse/DERBY-1410?page=all ]
Mike Matrigali updated DERBY-1410:
--
Fix Version: 10.2.0.0
Assign To: Mike Matrigali
SQL State DATA_SQLDATA_READ_ILLEGAL_ACCESS_EXCEPTION does not have a matching
message
[ http://issues.apache.org/jira/browse/DERBY-1410?page=all ]
Mike Matrigali resolved DERBY-1410:
---
Resolution: Fixed
m1_142:88svn commit
Sendingjava\engine\org\apache\derby\loc\messages_en.properties
Transmitting file data .
Committed
This is the later - I don't want the users to start the server.
BTW, I just prototyped a simple distributed peer-to-peer DataSource
[1]. In my tests I can run about 7 parallel processes on my MacBook
laptop that access the same database non-stop (each doing a select,
then insert, then
+1 for this release
I have tested 10.1.3 release candidate on Windows Server 2003 and Linux Suse 9.2. Summary and details of testing are as following:
Summary
-Mostly known failures
- Some failures which passed on rerun
Details
Windows Server 2003
ibm142
---
JVM: ibm142, Suite:
On 6/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
+XSDAN.S=Exception during restore of a SQLData object of class {0}. The
specified class cannot be encountered an illegal access exception.
Typo? Looks like the 'cannot be' snuck in by accident.
andrew
[ http://issues.apache.org/jira/browse/DERBY-937?page=all ]
Mike Matrigali updated DERBY-937:
-
Fix Version: 10.2.0.0
committed
Instability in wisconsin test
-
Key: DERBY-937
URL:
[ http://issues.apache.org/jira/browse/DERBY-937?page=all ]
Mike Matrigali updated DERBY-937:
-
committed change to trunk:
r418108 | mikem | 2006-06-29 11:27:51 -0700 (Thu, 29 Jun 2006) | 16 lines
DERBY-937, committing change by Andreas Korneliussen.
On 6/26/06, Andrew McIntyre [EMAIL PROTECTED] wrote:
Hello derby-dev,
I have posted a new release candidate for 10.1.3 here:
http://people.apache.org/~fuzzylogic/10.1.3.1/
+1 for my part.
On the 10.1.3.0 version I ran:
- Sun's j2ee cts suite (jdbc part only) with IBM jcc 2.6 (90) (all
[ http://issues.apache.org/jira/browse/DERBY-937?page=all ]
Mike Matrigali resolved DERBY-937:
--
Resolution: Fixed
I am closing this intermittent bug with fix committed as: 418108. If it
shows up again file a new issue with the new details.
+1 for 10.1.3 RC2
1. I had run the derbyall on AIX 5.2 with both IBM JDK142 and IBM
JDK1.5(With and without -Xjit:count=0 option).
2. Ran some system/stress test and the RC1 ran for more than a week
without any major issues (other than the known IBM1.5 issue, DERBY-1280)
and RC2 for 3 days.
There are currently 24 regression test failures listed in jira, I think
most apply to the trunk. Only one of them has anyone working on it.
I took a quick look at categorizing them. It seems like we should at
least spend some time on the mainline jvm (1.4, 1.5, 1.6) issues
verifying that
Andrew McIntyre wrote:
Hello derby-dev,
I have posted a new release candidate for 10.1.3 here:
http://people.apache.org/~fuzzylogic/10.1.3.1/
+1
Ran with the Derby tut at http://db.apache.org/derby/papers/DerbyTut as
well as the old ApacheCon 2004 tutorial at
[ http://issues.apache.org/jira/browse/DERBY-1017?page=all ]
Mike Matrigali updated DERBY-1017:
--
Component: SQL
(was: Network Server)
The most recent comment says this reproduces in embedded, so not a network
server issue. Setting
[ http://issues.apache.org/jira/browse/DERBY-1453?page=all ]
Mike Matrigali updated DERBY-1453:
--
Component: Network Client
Network Server
jdbcapi/blobclob4BLOB.java fails with 10.1 client and 10.2 server
Kristian Waagan wrote:
Hello,
When working on EmbedPreparedStatement.java, I noticed that a few
methods synchronize on the connection object, for instance addBatch. The
code typically looks like this:
synchronized (getConnectionSynchronization()) {
// Do stuff
}
The
[ http://issues.apache.org/jira/browse/DERBY-1450?page=all ]
Mike Matrigali updated DERBY-1450:
--
Component: Test
jdbcapi/parameterMetaDataJdbc30.java fails with 10.1 client and 10.2 server
[ http://issues.apache.org/jira/browse/DERBY-1387?page=all ]
Mike Matrigali updated DERBY-1387:
--
Component: Services
for lack of a better component made it services.
Add JMX extensions to Derby
---
Key:
[ http://issues.apache.org/jira/browse/DERBY-1452?page=all ]
Mike Matrigali updated DERBY-1452:
--
Component: Test
jdbcapi/resultset.java fails with 10.1 client and 10.2 server
-
HiAll,
I ran code coverage
for10.1.3 - svn revision no417277 with sun jdk131, sun jdk142, sun jdk15 on Windows 2000, and results are as following:-
OVERALL COVERAGE SUMMARY
Classes: 92% (1071/1167) Methods: 74% (14839/20030) Blocks: 71% (445925/630514) Lines: 71% (92693.9/130494)
OVERALL
[ http://issues.apache.org/jira/browse/DERBY-1458?page=all ]
Mike Matrigali updated DERBY-1458:
--
Component: Build tools
Add MessageBundleTest to build script to verify that there are no orphaned
message ids
Hi Mike,
+1 to cleaning these up for 10.2. I would also add the following bugs:
830 - lang/dcl.sql failures on solaris
1352 - sysinfo locale-specific noise
Regards,
-Rick
Mike Matrigali wrote:
There are currently 24 regression test failures listed in jira, I think
most apply to the trunk.
[Auto-generated mail]
*TinderBox_Derby* 418098/2006-06-29 19:53:05 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1675674 2 122.93% SunOS-5.10_i86pc-i386
Details in
+++1, we need to fix these
Rick Hillegas wrote:
Hi Mike,
+1 to cleaning these up for 10.2. I would also add the following bugs:
830 - lang/dcl.sql failures on solaris
1352 - sysinfo locale-specific noise
Regards,
-Rick
Mike Matrigali wrote:
There are currently 24 regression test failures
[ http://issues.apache.org/jira/browse/DERBY-1419?page=all ]
David Van Couvering reassigned DERBY-1419:
--
Assign To: David Van Couvering
derbyall/i18nTest/MessageBundleTest.diff test failed in nightly run, jdk15
[ http://issues.apache.org/jira/browse/DERBY-1419?page=all ]
David Van Couvering updated DERBY-1419:
---
Component: Services
(was: Regression Test Failure)
Priority: Minor (was: Major)
No longer a regression test failure, I
[ http://issues.apache.org/jira/browse/DERBY-551?page=all ]
Deepa Remesh updated DERBY-551:
---
Attachment: derby-551-draft1.diff
derby-551-draft1.status
ProcedureInTrigger_Tests_v1.html
Attaching a draft patch
[ http://issues.apache.org/jira/browse/DERBY-1032?page=all ]
Andrew McIntyre updated DERBY-1032:
---
Attachment: derby-1032-bin-sh.tgz
Attaching draft versions of new scripts for the bin directory. Batch files
based on the current batch files are next.
Andrew McIntyre wrote
=== SNIP ===
I will close this vote on Thursday, June 29 at 3:15 pm PDT. Please let
me know if you need more time to inspect/test the release candidate
and cast your vote.
Thanks again to everyone who has helped out with the release.
andrew
+1
I have run derbyall
[ http://issues.apache.org/jira/browse/DERBY-1435?page=all ]
Deepa Remesh updated DERBY-1435:
Attachment: repro1435_for_functions.sql
A similar case occurs when function/procedure referenced in triggered SQL
statement is dropped and a previously
[
http://issues.apache.org/jira/browse/DERBY-1449?page=comments#action_12418530 ]
Sunitha Kambhampati commented on DERBY-1449:
I tried this test out checkDataSource.java with 10.1 derbyclient.jar and
derbyTesting.jar, and rest are 10.2 jars
I have a question about the following page in jira:
http://issues.apache.org/jira/browse/DERBY?report=com.atlassian.jira.plugin.system.project:openissues-panel
Is the info here a standard we inherit from JIRA, or is it possible to
customize this view. Specifically what I would like is to have
On 6/26/06, Andrew McIntyre [EMAIL PROTECTED] wrote:
Hello derby-dev,
I have posted a new release candidate for 10.1.3 here:
http://people.apache.org/~fuzzylogic/10.1.3.1/
I almost forgot. +1 from me, too!
andrew
[ http://issues.apache.org/jira/browse/DERBY-1449?page=all ]
Deepa Remesh closed DERBY-1449:
---
Resolution: Invalid
Thanks for looking at this Sunitha and finding the cause. I agree this is a
test setup issue. The environment where this was run used
[Auto-generated mail]
*TinderBox_Derby* 418131/2006-06-29 22:33:00 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1675674 2 122.33% SunOS-5.10_i86pc-i386
Details in
On 6/29/06, Mike Matrigali [EMAIL PROTECTED] wrote:
I have a question about the following page in jira:
http://issues.apache.org/jira/browse/DERBY?report=com.atlassian.jira.plugin.system.project:openissues-panel
Is the info here a standard we inherit from JIRA, or is it possible to
customize
Bryan Pendleton wrote:
Sunitha Kambhampati commented on DERBY-1449:
I tried this test out checkDataSource.java with 10.1
derbyclient.jar and derbyTesting.jar,
and rest are 10.2 jars and followed instructions to run with new
server/old client
It seems that some comments to Jira entries are again not making it to
the derby-dev list. For example Rick's comment on DERBY-1459 at
28/Jun/06 09:52 PM doesn't seem to be in the archives or my in-folder.
http://issues.apache.org/jira/browse/DERBY-1459?page=all
It's a big concern if people are
On 6/29/06, Daniel John Debrunner [EMAIL PROTECTED] wrote:
It seems that some comments to Jira entries are again not making it to
the derby-dev list. For example Rick's comment on DERBY-1459 at
28/Jun/06 09:52 PM doesn't seem to be in the archives or my in-folder.
Andrew McIntyre wrote:
I got it.
Found it here:
Mail client / ISP problem?
Dan problem I think, maybe the shakes from the lack of world cup soccer
the last two days. :-)
Thanks for checking, sorry for the disturbance.
Dan.
Andrew McIntyre wrote:
I am now closing this vote to release 10.1.3. The vote passes with
fifteen +1s and no zero or negative votes.
Darn, missed the boat, +1 from me.
Dan.
Andrew McIntyre wrote:
On 6/29/06, Mike Matrigali [EMAIL PROTECTED] wrote:
I have a question about the following page in jira:
http://issues.apache.org/jira/browse/DERBY?report=com.atlassian.jira.plugin.system.project:openissues-panel
I am in the process of making a Wiki page for Jira
The release notes draft page is here:
http://people.apache.org/~fuzzylogic/releases/release-10.1.3.1.html
Ignore the formatting, it's missing one of the CSS files. I still need
to fill in the test results and the link to the 'list of fixed
issues'. Let me know if I've missed anything else.
I have some tests that I run against the Derby Server using the IBM DB2 ODBC
client and I've noticed that, for scrollable cursors, the client returns the
first row *twice* now that the Derby Server supports pre-fetching (DERBY-822).
Long story short someone who works with the client pointed
Deepa Remesh wrote:
Seeing these additional failures in the client/server compat tests.
These seem to be expected but just wanted to get feedback from others
in case we need to do something extra:
* derbynet/testProtocol.java (after DERBY-959)
The max query blocksize that is allowed in the
Long story short someone who works with the client pointed out that the
client is sending a QRYROWSET of size 0 when it sends the OPNQRY
Hi Army,
Page 698 of V.3 says:
A QRYROWSET value of zero on the OPNQRY and EXCSQLSTT commands instructs
the server to return no rows with the OPNQRYRM
[ http://issues.apache.org/jira/browse/DERBY-655?page=all ]
Mamta A. Satoor resolved DERBY-655:
---
Fix Version: 10.2.0.0
Resolution: Fixed
Resolving this issue since the patch ensures the uniqueness of conglomerateid
for new conglomerates in
92 matches
Mail list logo
