[ http://issues.apache.org/jira/browse/DERBY-408?page=all ]
Jeff Levitt updated DERBY-408:
--
Summary: Fix formatting of manuals in PDF output (was: Fix formatting
of syntax sections in manuals)
Description:
1. The syntax boxes in many of the
[
http://issues.apache.org/jira/browse/DERBY-416?page=comments#action_12314738 ]
Mamta A. Satoor commented on DERBY-416:
---
The problem was with using ' in the error text message ie the text for XJ084 in
messages_en.properties currently looks like
I have attached a patch to Derby-416 Parameter in one of the error messages is not replaced by the desired value
If the patch looks good, can a commiter please commit this?
thanks,
Mamta
On 6/29/05, Mamta A. Satoor (JIRA) derby-dev@db.apache.org wrote:
[
On Jun 29, 2005, at 11:20 PM, Mamta Satoor wrote:
I have attached a patch to Derby-416 Parameter in one of the error
messages is not replaced by the desired value
If the patch looks good, can a commiter please commit this?
thanks,
Mamta
This looks like a very straightforward fix. I'll
[ http://issues.apache.org/jira/browse/DERBY-416?page=all ]
Andrew McIntyre resolved DERBY-416:
---
Fix Version: 10.1.1.0
10.2.0.0
Resolution: Fixed
Committed, revision 202492 to trunk. Will merge to 10.1 branch before
Beetle6038.java store test fails on Mac OS X
Key: DERBY-417
URL: http://issues.apache.org/jira/browse/DERBY-417
Project: Derby
Type: Test
Components: Test
Versions: 10.1.1.0, 10.2.0.0
Environment: Mac OS X
[ http://issues.apache.org/jira/browse/DERBY-382?page=all ]
Jeff Levitt updated DERBY-382:
--
Comment: was deleted
Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual
---
Thanks for the tips Dan. Attached to this list is a text file outlining
some of the more important points of this patch.
Also in case an executive summary would be useful to anyone there are a
few of main points that I tried to address with this patch (in order of
importance):
- Remove the
It's a bit unclear if you are still unable to compile or you are just
commenting on the build process. If you are still having problems a few
things to consider:
- Make sure the ant.properties file is actually in your user.home
directory. For me in a windows environment this is (as default)
Philip Wilder wrote:
In regards to your last challenge, I am inclined to agree with your
position. If we consistently follow the specs over the javadocs that is
one less point for confusion. However as Kathey points out, this may
mean that there are bugs in the javadocs. If we adopt this
Daniel John Debrunner wrote:
Daniel John Debrunner wrote:
Daniel John Debrunner wrote:
I had to re-run the tests because the patch messed up on one file, but
now StmtCloseFunTest fails for me with this patch.
*** Start: StmtCloseFunTest jdk1.4.2 derbyall:jdbc20 2005-06-28 22:08:57 ***
2a3
Is this problem specific to network client?
Kathey Marsden (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-414?page=all ]
Kathey Marsden updated DERBY-414:
-
Attachment: deby414Repro.zip
run repro as
java TestDerbyNSXA
Client
[
http://issues.apache.org/jira/browse/DERBY-276?page=comments#action_12314781 ]
Daniel John Debrunner commented on DERBY-276:
-
I'll look at committing this, it seems to have been forgotten about. :-(
ResultSet.relative(int row) cannot be
Mike Matrigali wrote:
Is this problem specific to network client?
Yes. if you switch the repro to use embedded all seems to work ok.
[
http://issues.apache.org/jira/browse/DERBY-405?page=comments#action_12314789 ]
Satheesh Bandaram commented on DERBY-405:
-
The behavior here is same as with views. Suspect this is because of statement
caching. We don't seem to recognise we have a
[
http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314790 ]
Jean T. Anderson commented on DERBY-382:
I forgot to add this comment earlier, discussed with Jeff and he agreed I
should go ahead and post now because it cites a
[
http://issues.apache.org/jira/browse/DERBY-405?page=comments#action_12314793 ]
Daniel John Debrunner commented on DERBY-405:
-
Well, SYNONYM's haven't been released yet, thus we could disallow SYNONYMs in
SESSION schema, before 10.1 goes GA.
[
http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314794 ]
Jean T. Anderson commented on DERBY-382:
CREATE FUNCTION at
http://incubator.apache.org/derby/docs/ref/rrefcreatefunctionstatement.html
doesn't show an example,
[ http://issues.apache.org/jira/browse/DERBY-406?page=all ]
Philip Wilder reassigned DERBY-406:
---
Assign To: Philip Wilder
Client DataSource should not require user property to be set
ok, then it seems like somehow the network client is not setting the
right isolation level - rather than isolation level stuff in the server
not working.
I am not sure what it takes to get tests running against network server
but the following tests in the embedded server test out a lot of
[
http://issues.apache.org/jira/browse/DERBY-31?page=comments#action_12314795 ]
Daniel John Debrunner commented on DERBY-31:
Øyvind's patch committed revision 208650. (into trunk)
Statement.setQueryTimeout() support.
[
http://issues.apache.org/jira/browse/DERBY-405?page=comments#action_12314796 ]
Mamta A. Satoor commented on DERBY-405:
---
I agree with Dan's response but I think we have a bug here with statement
caching. If I recall correctly, I think the goal was
[
http://issues.apache.org/jira/browse/DERBY-405?page=comments#action_12314797 ]
Satheesh Bandaram commented on DERBY-405:
-
Dan's suggestion is good... We should disable synonyms in SESSION schema. I
will submit a patch soon.
I will also file
[ http://issues.apache.org/jira/browse/DERBY-390?page=all ]
Suresh Thalamati updated DERBY-390:
---
Attachment: derby390.diff
patch to handle case-sensitive SQL identifiers correctly. Import/export
procedure parameters for
table names , schema
Mike Matrigali wrote:
ok, then it seems like somehow the network client is not setting the
right isolation level - rather than isolation level stuff in the server
not working.
I am not sure what it takes to get tests running against network server
but the following tests in the embedded server
Something that is different for XA is that each transaction tends
to get a lot more context rebuilt then for normal connection (this
is because other threads can pick up and enter a global transaction).
I wonder if the isolation gets set ok the first time, but then gets
lost?
Kathey Marsden
[
http://issues.apache.org/jira/browse/DERBY-398?page=comments#action_12314801 ]
Daniel John Debrunner commented on DERBY-398:
-
I think for all the new files you've added (test_app.properties) to exclude
tests for J2ME Foundation, the correct
outofmemory error when running large query in autocommit=false mode
---
Key: DERBY-418
URL: http://issues.apache.org/jira/browse/DERBY-418
Project: Derby
Type: Bug
Components: Store
Versions:
[ http://issues.apache.org/jira/browse/DERBY-418?page=all ]
Sunitha Kambhampati updated DERBY-418:
--
Attachment: AutoCommitTest.java
This repro was given by Chris.
http://www.mail-archive.com/derby-user@db.apache.org/msg01258.html.
To run
java
[ http://issues.apache.org/jira/browse/DERBY-384?page=all ]
Jeff Levitt updated DERBY-384:
--
Attachment: derby384.diff
The attached patch makes the changes requested in this doc review. I have
created sample output on my own site:
HTML files:
[ http://issues.apache.org/jira/browse/DERBY-276?page=all ]
Daniel John Debrunner updated DERBY-276:
Fix Version: 10.2.0.0
Description:
If the cursor is not positioned on a row, calling ResultSet.relative() causes
the following exception:
[ http://issues.apache.org/jira/browse/DERBY-31?page=all ]
Daniel John Debrunner updated DERBY-31:
---
Fix Version: 10.2.0.0
Statement.setQueryTimeout() support.
Key: DERBY-31
URL:
I have not implemented metadata support. It could be taken up as
another item. I probably will...
Satheesh
Mamta Satoor wrote:
Hi Satheesh,
Just wondered if you got a chance to look at following. Also, if
this is supported then is there a test for it?
thanks,
Mamta
On
[
http://issues.apache.org/jira/browse/DERBY-414?page=comments#action_12314823 ]
Kathey Marsden commented on DERBY-414:
--
If I move the setTransactionIsolation to after the start of the xa transaction
the isolation level gets set properly.
It would
Support direct execution of derbynet.jar using the -jar option of the VM.
-
Key: DERBY-419
URL: http://issues.apache.org/jira/browse/DERBY-419
Project: Derby
Type: Improvement
Components:
missing classes in published javadoc incorrect copyright date
---
Key: DERBY-420
URL: http://issues.apache.org/jira/browse/DERBY-420
Project: Derby
Type: Bug
Components: Documentation
Versions:
[ http://issues.apache.org/jira/browse/DERBY-384?page=all ]
Andrew McIntyre resolved DERBY-384:
---
Resolution: Fixed
Committed, revision 208690.
Doc Review (CLOSED TO FURTHER COMMENTS): Tuning Derby
[
http://issues.apache.org/jira/browse/DERBY-377?page=comments#action_12314825 ]
Suresh Thalamati commented on DERBY-377:
Looks good to me.I am not sure of the following statements , In the
Upgrades section ,
whether on upgrade from 10.0 to
[
http://issues.apache.org/jira/browse/DERBY-377?page=comments#action_12314826 ]
Daniel John Debrunner commented on DERBY-377:
-
Review comments:
Soft Upgrade
---
Replace
'a soft upgrade allows you to upgrade an older Derby
[ http://issues.apache.org/jira/browse/DERBY-379?page=all ]
Andrew McIntyre resolved DERBY-379:
---
Resolution: Fixed
Committed modified patch, revision 208692.
Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby
starting an XA transaction resets the isolation level set with SET CURRENT
ISOLATION
Key: DERBY-421
URL: http://issues.apache.org/jira/browse/DERBY-421
Project: Derby
Type:
[ http://issues.apache.org/jira/browse/DERBY-414?page=all ]
Kathey Marsden updated DERBY-414:
-
Summary: With Network Client starting an XA transaction resets the
isolation level set with setTransactionIsolation (was: Client XA has a problem
with
[ http://issues.apache.org/jira/browse/DERBY-383?page=all ]
Andrew McIntyre resolved DERBY-383:
---
Resolution: Fixed
Committed, revision 208693.
Doc Review (CLOSED TO FURTHER COMMENTS): Derby Tools and Utilities Guide
[ http://issues.apache.org/jira/browse/DERBY-381?page=all ]
Andrew McIntyre resolved DERBY-381:
---
Resolution: Fixed
Committed, revision 208694.
Doc review (CLOSED TO FURTHER COMMENTS): Derby Server and Admin Guide
Queryplan for a query using SESSION schema view is incorrectly put in statement
cache. This could cause incorrect plan getting executed later if a temp. table
is created with that name.
[ http://issues.apache.org/jira/browse/DERBY-405?page=all ]
Satheesh Bandaram resolved DERBY-405:
-
Resolution: Fixed
Fix has been merged into trunk. This may get ported to 10.1, if Andrew, the
release czar, decides this is important for 10.1
[
http://issues.apache.org/jira/browse/DERBY-405?page=comments#action_12314833 ]
Satheesh Bandaram commented on DERBY-405:
-
Jeff, can you alter CREATE SYNONYM section to say creating synonyms in SESSION
schema is not allowed?
SYNONYM should not
[ http://issues.apache.org/jira/browse/DERBY-382?page=all ]
Jeff Levitt updated DERBY-382:
--
Attachment: derby382.diff
The attached patch makes the changes requested in this doc review. I have
created sample output on my own site:
HTML files:
[
http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314834 ]
Jeff Levitt commented on DERBY-382:
---
Forgot to change the links in my posting template to point to the ref manual on
my site:
http://derby.mylevita.com/ref/refderby.pdf
[ http://issues.apache.org/jira/browse/DERBY-424?page=all ]
Satheesh Bandaram updated DERBY-424:
Version: 10.2.0.0
Queryplan for a query using SESSION schema view is incorrectly put in
statement cache. This could cause incorrect plan getting
[ http://issues.apache.org/jira/browse/DERBY-377?page=all ]
Andrew McIntyre resolved DERBY-377:
---
Resolution: Fixed
Committed, revision 208695.
There is no information available in the manuals on how to upgrade a
database from 10.0 to 10.1
[
http://issues.apache.org/jira/browse/DERBY-420?page=comments#action_12314837 ]
Andrew McIntyre commented on DERBY-420:
---
I checked in a fix for the missing classes to the trunk and posted a copy for
review on my public_html:
[ http://issues.apache.org/jira/browse/DERBY-424?page=all ]
Mamta A. Satoor reassigned DERBY-424:
-
Assign To: Mamta A. Satoor
Queryplan for a query using SESSION schema view is incorrectly put in
statement cache. This could cause incorrect plan
[ http://issues.apache.org/jira/browse/DERBY-382?page=all ]
Andrew McIntyre resolved DERBY-382:
---
Resolution: Fixed
Applied provided patch with revision 208698. Further comments should be
attached to issue DERBY-423.
Doc Review (CLOSED TO
This is a minor issue, and I wasnt sure whether it was
something that needed a JIRA issue. I've noticed that
some of the html output files for the docs that have
been removed from the manuals for whatever reason are
still on the server. It might be nice to clear out
those directories every now
[
http://issues.apache.org/jira/browse/DERBY-380?page=comments#action_12314839 ]
Jeff Levitt commented on DERBY-380:
---
Suresh requested in Derby-377 (too late for that commit):
In preparing for Upgrade section , Following step is not required:
1.
Force
Now the client objects are part of the published api I did some cleanup
of the javadoc comments, attached is the patch. I'll commit assuming no
objections once my derbyall tests run.
M org\apache\derby\jdbc\ClientXADataSource.java
M
documentation need to be modified to reflect the derby-390 fix(once it is
committed) , schem , table , column names need to be in case-sensitive form.
[
http://issues.apache.org/jira/browse/DERBY-390?page=comments#action_12314842 ]
Suresh Thalamati commented on DERBY-390:
Same patch (derby390.diff) also works fine for 10.1 branch also. Ran Derbyall
on 10.1 after applying the patch for a 10.1
[
http://issues.apache.org/jira/browse/DERBY-385?page=comments#action_12314843 ]
Myrna van Lunteren commented on DERBY-385:
--
When this gets fixed, maybe it makes sense to fix up the comments re
db2j.locale and db2j.codeset.
servlet Back to Main
[
http://issues.apache.org/jira/browse/DERBY-377?page=comments#action_12314852 ]
Andrew McIntyre commented on DERBY-377:
---
Jeff - The patch file provided in the zip, derby377modified.diff, did not
contain the source file for tdevpreupgrade.html
An error message when running in Derby Network Server says cloudscape.LOG
rather than derby.log
---
Key: DERBY-427
URL: http://issues.apache.org/jira/browse/DERBY-427
Project: Derby
[
http://issues.apache.org/jira/browse/DERBY-377?page=comments#action_12314853 ]
Andrew McIntyre commented on DERBY-377:
---
Jeff - The patch file provided in the zip, derby377modified.diff, did not
contain the source file for tdevpreupgrade.html
[ http://issues.apache.org/jira/browse/DERBY-385?page=all ]
Myrna van Lunteren updated DERBY-385:
-
Attachment: servlet_385.diff
this will probably make patch for derby-117 no longer work.
servlet Back to Main Page link points to csnet instead of
[ http://issues.apache.org/jira/browse/DERBY-427?page=all ]
Mamta A. Satoor updated DERBY-427:
--
Component: Unknown
(was: Network Client)
Summary: An error message when running in XA environment says
cloudscape.LOG rather
65 matches
Mail list logo
