It seems to me that these messages can never ever been verified. Also
in the case where values are provided, it does not match the leading
text. (E.g., location is given as the first parameter, but should have
been the third.) See my comment in another thread
[ http://issues.apache.org/jira/browse/DERBY-1176?page=all ]
Knut Anders Hatlen closed DERBY-1176:
-
Fix Version: 10.2.0.0
Resolution: Fixed
Committed revision 395799.
Stored prepared statements in the SYSIBM schema are not updated on
Andrew McIntyre [EMAIL PROTECTED] wrote:
What version of svn / svnversion are you using? I'm using 1.2.0, and
I'm not seeing this problem. Even if I cd to tools/testing/derby and
svn up the external directory to a new revision, my Derby basedir
still reports the same revision without a range.
[
http://issues.apache.org/jira/browse/DERBY-1237?page=comments#action_12375519 ]
Knut Anders Hatlen commented on DERBY-1237:
---
The same error appeared in the tinderbox test yesterday (Sun JVM 1.5, Solaris
10 x86), but it was (incorrectly?)
[Auto-generated mail]
*Derby* 395659/2006-04-20 19:46:06 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.6*
NA NA NANA SunOS-5.10_i86pc-i386
Details in
[ http://issues.apache.org/jira/browse/DERBY-925?page=all ]
Dyre Tjeldvoll resolved DERBY-925:
--
Fix Version: 10.2.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Implement new JDBC 4 metadata API getFunctionParameters()
Write test(s) for ParameterMetaData and the getParameterMetaData-methods in
JDBC4
-
Key: DERBY-1242
URL: http://issues.apache.org/jira/browse/DERBY-1242
Project: Derby
Type: Test
Olav Sandstaa [EMAIL PROTECTED] wrote:
Andrew McIntyre [EMAIL PROTECTED] wrote:
What version of svn / svnversion are you using? I'm using 1.2.0, and
I'm not seeing this problem. Even if I cd to tools/testing/derby and
svn up the external directory to a new revision, my Derby basedir
still
[ http://issues.apache.org/jira/browse/DERBY-1093?page=all ]
Dyre Tjeldvoll updated DERBY-1093:
--
Attachment: derby-1093.v2.diff
derby-1093.v2.stat
derbyall_report.v2.txt
Although there are still two blocking issues open,
[
http://issues.apache.org/jira/browse/DERBY-1093?page=comments#action_12375530 ]
Knut Anders Hatlen commented on DERBY-1093:
---
The patch looks good. I have started a test run and plan to commit the patch if
it runs cleanly.
Make
Dag H. Wanvik wrote:
John H. Embretsen (JIRA) derby-dev@db.apache.org writes:
[
http://issues.apache.org/jira/browse/DERBY-1194?page=comments#action_12374701
]
John H. Embretsen commented on DERBY-1194:
--
Here is another suggestion which captures
Ok. I'll commit this one.
Dag H. Wanvik (JIRA) wrote (2006-04-20 15:17:06):
[ http://issues.apache.org/jira/browse/DERBY-775?page=all ]
Dag H. Wanvik updated DERBY-775:
Attachment: derby-775-7.stat
derby-775-7.diff
Patch did
[ http://issues.apache.org/jira/browse/DERBY-775?page=all ]
Bernt M. Johnsen resolved DERBY-775:
Resolution: Fixed
Derby Info: [Patch Available, Release Note Needed] (was: [Release Note
Needed, Patch Available])
Committed revision 395866.
[ http://issues.apache.org/jira/browse/DERBY-876?page=all ]
Knut Anders Hatlen updated DERBY-876:
-
Attachment: derby-876-v1.diff
derby-876-v1.stat
Attaching a patch which adds the TABLE_CATALOG column to the result
set returned by
[ http://issues.apache.org/jira/browse/DERBY-876?page=all ]
Knut Anders Hatlen updated DERBY-876:
-
Derby Info: [Patch Available]
DatabaseMetaData.getSchemas() is not JDBC 3.0 compliant
---
[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ]
Kristian Waagan updated DERBY-1180:
---
Attachment: derby-1180-1a-embedded.diff
derby-1180-1a-embedded.stat
'derby-1180-1a-embedded.diff' addresses missing JDBC4 signatures on
[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ]
Kristian Waagan updated DERBY-1180:
---
Derby Info: [Patch Available]
Partial patch 'derby-1180-1a-embedded.diff' available.
Add vacuous implementations of missing JDBC4 methods
Deepa Remesh [EMAIL PROTECTED] wrote:
The tests in the harness use ij.startJBMS to get initial connections.
The connection is obtained by using the properties specified in the
test_app.properties file. ij.startJBMS method can also be used for
any subsequent connections which use same
Suresh Thalamati [EMAIL PROTECTED] wrote:
By looking at the stack it looks like log/logmirror.ctrl is not
getting accessed in the privileged block at line 2940 in LogToFile.java.
if (checkpointInstant == LogCounter.INVALID_LOG_INSTANT
[
http://issues.apache.org/jira/browse/DERBY-1180?page=comments#action_12375554 ]
Knut Anders Hatlen commented on DERBY-1180:
---
Committed revision 395872.
I see 11 missing signatures when running jdbc4/VerifySignatures.junit, but
that's probably
[
http://issues.apache.org/jira/browse/DERBY-1180?page=comments#action_1237 ]
Dyre Tjeldvoll commented on DERBY-1180:
---
I have looked at the patch, and I think it looks good, but I have a coule of
observations:
- EmbedBlob.getBinaryStream() seems
[
http://issues.apache.org/jira/browse/DERBY-876?page=comments#action_12375557 ]
Dyre Tjeldvoll commented on DERBY-876:
--
I have looked at the v1 patch and I think it looks good. I think it can be
committed.
DatabaseMetaData.getSchemas() is not JDBC
[
http://issues.apache.org/jira/browse/DERBY-1180?page=comments#action_12375558 ]
Kristian Waagan commented on DERBY-1180:
All the comments are valid, but since I am only adding placeholders that throw
not implemented exceptions, I decided to not
[ http://issues.apache.org/jira/browse/DERBY-1093?page=all ]
Knut Anders Hatlen resolved DERBY-1093:
---
Resolution: Fixed
Committed revision 395877.
Dyre, if you haven't already done so, could you please file a JIRA issue for
the ODBC
[ http://issues.apache.org/jira/browse/DERBY-876?page=all ]
Knut Anders Hatlen resolved DERBY-876:
--
Fix Version: 10.2.0.0
Resolution: Fixed
Thanks for reviewing, Dyre! Committed revision 395878.
DatabaseMetaData.getSchemas() is not JDBC
[ http://issues.apache.org/jira/browse/DERBY-1090?page=all ]
Olav Sandstaa updated DERBY-1090:
-
Attachment: client1090_patch1.diff
This patch (client1090_patch1.diff) implements the Connection.isValid for the
network client. The connection is valid if
[ http://issues.apache.org/jira/browse/DERBY-1090?page=all ]
Olav Sandstaa updated DERBY-1090:
-
Derby Info: [Patch Available]
Implement Connection.isValid as defined by JDBC4
Key: DERBY-1090
Modify ODBCMetaDataGenerator to use the JDBC4 version of metadata queires as
input
--
Key: DERBY-1243
URL: http://issues.apache.org/jira/browse/DERBY-1243
Project: Derby
Type:
[ http://issues.apache.org/jira/browse/DERBY-1093?page=all ]
Dyre Tjeldvoll closed DERBY-1093:
-
Make DatabaseMetaData.getProcedures() JDBC4 compliant
-
Key: DERBY-1093
URL:
[ http://issues.apache.org/jira/browse/DERBY-514?page=all ]
Deepa Remesh updated DERBY-514:
---
Attachment: derby-514-patch5-addtoderbyall.diff
derby-514-patch5-addtoderbyall.status
Attaching a patch 'derby-514-patch5-addtoderbyall.diff'
[ http://issues.apache.org/jira/browse/DERBY-1237?page=all ]
Kathey Marsden updated DERBY-1237:
--
Summary: unit/daemonService fails intermittently with (was:
unit/daemonService fails with IBM 1.4.2)
Changing the summary to not just be ibm 1.4.2
[
http://issues.apache.org/jira/browse/DERBY-1090?page=comments#action_12375577 ]
Dyre Tjeldvoll commented on DERBY-1090:
---
I have looked at the patch, and I think it looks good, and can be committed.
Implement Connection.isValid as defined by JDBC4
[ http://issues.apache.org/jira/browse/DERBY-1237?page=all ]
Kathey Marsden updated DERBY-1237:
--
Summary: unit/daemonService fails intermittently with Shutting down due
to unit test failure. (was: unit/daemonService fails intermittently with)
[Auto-generated mail]
*TinderBox_Derby* 395866/2006-04-21 14:12:45 CEST
*derbyall*
Failed TestsOK Skip Duration Platform
---
*Jvm: 1.5*
1653652 0 141.71% SunOS-5.10_i86pc-i386
Details in
[ http://issues.apache.org/jira/browse/DERBY-1141?page=all ]
John H. Embretsen updated DERBY-1141:
-
Attachment: JUnit_useprocessFalse_v1.diff
Attaching 'JUnit_useprocessFalse_v1.diff'
This patch is _not_ ready for commit (I have not tested it
On 4/21/06, Deepa Remesh (JIRA) derby-dev@db.apache.org
wrote:
NOTE:The pre-requisites to run upgrade tests:* If the tests are run on a machine where the svn source is not available, a property '
derbyTesting.jar.path' needs to be set in ant.properties file. Details are in Section 3.2 in
On 4/21/06, Myrna van Lunteren [EMAIL PROTECTED] wrote:
On 4/21/06, Deepa Remesh (JIRA) derby-dev@db.apache.org wrote:
NOTE:
The pre-requisites to run upgrade tests:
* If the tests are run on a machine where the svn source is not available,
a property ' derbyTesting.jar.path' needs to be
ij no longer returns error messages based on derby.ui.locale
Key: DERBY-1244
URL: http://issues.apache.org/jira/browse/DERBY-1244
Project: Derby
Type: Bug
Components: Tools
Versions: 10.2.0.0
On 4/21/06, Deepa Remesh [EMAIL PROTECTED] wrote:
Ant is not required to run the test. As usual, ant is requiredonly during build. During build, the value specified in the
ant.properties file will be used to update the test's app_propertiesfile so that the test knows where to look for the jars
[ http://issues.apache.org/jira/browse/DERBY-1244?page=all ]
Andrew McIntyre reassigned DERBY-1244:
--
Assign To: Andrew McIntyre
ij no longer returns error messages based on derby.ui.locale
I had to look into this when I was playing around with a classloader for
code sharing.
Basically, by setting the serialVersionUID, you are telling the VM that
you guarantee that the newer version of the class is compatible with the
old version (in terms of serialization).
If you don't set
Thanks, Øystein, that was what I determined also. I fixed the placement
of arguments so they are correct. But I have to think about your point
of this information not being useful. I tend to agree, I think the
stack trace should be sufficient actually. There's not a lot of useful
On 4/21/06, Myrna van Lunteren [EMAIL PROTECTED] wrote:
Then build, and then I need to copy the 10.1 jars to c:\10jars\10.1? And the
10.2 jars can still be anywhere?
10.2 jars can be anywhere, set in your classpath. 10.1 jars can be
anywhere, There are multiple ways to set the location of the
[ http://issues.apache.org/jira/browse/DERBY-1127?page=all ]
Sunitha Kambhampati updated DERBY-1127:
---
Attachment: for_10.1_derby1127.p1.diff.txt
NewTestEnc.java
I am attaching a patch for 10.1 codeline
Thanks, David. I'm afraid I'm still muddled. I think I understand the
basic purpose of serialVersionUID: It's a compiler-generated checksum of
the source which serialization uses as a sanity check. By explicitly
setting this field, the engineer promises to keep the following
contract: Although
[
http://issues.apache.org/jira/browse/DERBY-1244?page=comments#action_12375619 ]
Anders Morken commented on DERBY-1244:
--
Works for me, using both jars and classes from a freshly built rev 395950.
[EMAIL PROTECTED] tmp]$ java -cp
Hi Rick,
once the serialVerisonUID is there, you should not remove it as chaos
can break out if the IDs start to differ. IMHO would leave them alone.
One example is you have say someone using say derby version x with a an
ID of 1 and then persisted the object... now u remove the ID in derby
I am less convinced that it can't be changed. The alternate approach to
the one I proposed would be:
I feel like there is general consensus about this topic, although that
might be surprising because several opinions and proposals have been
stated so far. Let me state what I think the general
[ http://issues.apache.org/jira/browse/DERBY-1127?page=all ]
Sunitha Kambhampati updated DERBY-1127:
---
Attachment: for_10.1_derby1127.p1.v2.diff.txt
Please use this patch (for_10.1_derby1127.p1.v2.diff.txt) for 10.1 codeline -
a one line change
On 4/21/06, Deepa Remesh [EMAIL PROTECTED] wrote:
On 4/21/06, Andrew McIntyre [EMAIL PROTECTED] wrote:
On 4/21/06, Myrna van Lunteren [EMAIL PROTECTED] wrote:
Then build, and then I need to copy the 10.1 jars to c:\10jars\10.1? And
the
10.2 jars can still be anywhere?
10.2 jars
On 4/21/06, Deepa Remesh [EMAIL PROTECTED] wrote:
On 4/21/06, Deepa Remesh [EMAIL PROTECTED] wrote: On 4/21/06, Andrew McIntyre
[EMAIL PROTECTED] wrote: On 4/21/06, Myrna van Lunteren [EMAIL PROTECTED] wrote:
Then build, and then I need to copy the 10.1 jars to c:\10jars\10.1? And the
FYI, the attached emails provides some guidance on who an appropriate
mentor is.
David
---BeginMessage---
On 4/21/06, David W. Van Couvering [EMAIL PROTECTED] wrote:
I just wanted to clarify: can anyone be a mentor, or does it have to be
a committer?
Our preference is for ASF members or
Bryan Pendleton wrote:
1) There are two basic configurations of interest here:
a) In the simple Network Server case, the Network Server process
is providing access to the database(s) over DRDA
b) In the dual-access configuration, an application which has
established
[ http://issues.apache.org/jira/browse/DERBY-677?page=all ]
Knut Anders Hatlen closed DERBY-677:
Resolution: Won't Fix
Since we have runnable jar files now, there is no need to rewrite the ksh
scripts. Closing the issue with resolution won't
Hi, all. Students can make proposals from May 1 to May 8. The ASF page
http://wiki.apache.org/general/SummerOfCode2006 is the official ideas
page for the ASF that students will be looking at, and probably already are.
I just updated http://wiki.apache.org/db-derby/CodingProjects with some
I'm getting errors like the following when I build the user docs. Would
appreciate advice about how to fix this. Thanks-Rick
[echo]
*
[echo] * input =
This is http://issues.apache.org/jira/browse/DERBY-1215 .
But the build should succeed at the end. Does the build fail for you?
-jean
Rick Hillegas wrote:
I'm getting errors like the following when I build the user docs. Would
appreciate advice about how to fix this. Thanks-Rick
David W. Van Couvering wrote:
My understanding was that they may persist across upgrades because the
data source objects are serialized into a JNDI store. In general we
can *add* non-transient fields but we can't remove or change them.
Thanks for that warning about the JNDI store. It would
Rick Hillegas wrote:
David W. Van Couvering wrote:
My understanding was that they may persist across upgrades because
the data source objects are serialized into a JNDI store. In general
we can *add* non-transient fields but we can't remove or change them.
Thanks for that warning about
[
http://issues.apache.org/jira/browse/DERBY-1090?page=comments#action_12375649 ]
Rick Hillegas commented on DERBY-1090:
--
I concur, looks good. JDBC4 tests run cleanly. Derbyall runs cleanly modulo
wisconsin noise. Committed at subversion revision
[ http://issues.apache.org/jira/browse/DERBY-972?page=all ]
Sunitha Kambhampati updated DERBY-972:
--
Derby Info: [Patch Available]
Patch available for review/commit - derby972.diff.txt. Thanks.
tests derbynet/csPrepStmt and prepStmt use
Thanks, Lance. This is a very sensible suggestion.
Regards,
-Rick
Lance J. Andersen wrote:
People do strange things. We in the Java SE land have tests which
save serialized object and then test that they can be deserialized
with the next revision. I would suggest adding some tests to the
Thanks, Jean. The build did churn to the end and Ant reported BUILD
SUCCESSFUL. The docs look ok. Thanks for setting my mind at ease!
Regards,
-Rick
Jean T. Anderson wrote:
This is http://issues.apache.org/jira/browse/DERBY-1215 .
But the build should succeed at the end. Does the build fail
Right, can't you override the readObject method or whatever it's called?
(Sorry, too lazy to look up the javadoc)
I have some tests, Rick. If you'd like I can send them to you.
Alternately log a JIRA and I can attach the source to the JIRA.
Can't actually spend the time to fully implement
Add o.a.derby.client.am.ClobWriter test coverage
Key: DERBY-1245
URL: http://issues.apache.org/jira/browse/DERBY-1245
Project: Derby
Type: Sub-task
Reporter: Anders Morken
Assigned to: Anders Morken
--
[ http://issues.apache.org/jira/browse/DERBY-1245?page=all ]
Anders Morken updated DERBY-1245:
-
Component: Network Client
Test
Fix Version: 10.2.0.0
Description: org.apache.derby.client.am.ClobWriter.java is currently not
David W. Van Couvering wrote:
Hi, all. Students can make proposals from May 1 to May 8. The ASF page
http://wiki.apache.org/general/SummerOfCode2006 is the official ideas
page for the ASF that students will be looking at, and probably already
are.
I just updated
[
http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12375656 ]
Andrew McIntyre commented on DERBY-1078:
Committed revision 396035 which fixes the remaining issues in the tests built
with JDK 1.5 or higher and then run on JDK 1.3.
[
http://issues.apache.org/jira/browse/DERBY-1229?page=comments#action_12375657 ]
Bryan Pendleton commented on DERBY-1229:
Can you confirm that if you add the following line to derby_tests.policy, the
problem goes away? The line should be added to
[
http://issues.apache.org/jira/browse/DERBY-913?page=comments#action_12375662 ]
Stan Bradbury commented on DERBY-913:
-
I've double checked the DITA files and it does not appear to be a syntax error
in the files. I'm guessing it is a problem with the
[
http://issues.apache.org/jira/browse/DERBY-913?page=comments#action_12375664 ]
Jean T. Anderson commented on DERBY-913:
Only the new Working With Derby doc fails to build on Linux, the other Derby
docs build successfully, so perhaps there's a
[
http://issues.apache.org/jira/browse/DERBY-1244?page=comments#action_12375672 ]
Andrew McIntyre commented on DERBY-1244:
I also was not able to reproduce the problem on my machine, but after
reinspecting the code, it does appear that we would
72 matches
Mail list logo
