[ http://issues.apache.org/jira/browse/DERBY-377?page=all ]
Jeff Levitt updated DERBY-377:
--
Attachment: derby377addendum.diff
Thanks for the catch Andrew. I guess I didnt svn add it the first time. The
attached patch called derby377addendum.diff is an
NetworkClient PreparedStatement.executeBatch() hangs if batch is too large
(ArrayIndexOutOfBoundsException in Network Server)
-
Key: DERBY-428
URL:
Doc Review : Derby Tools and Utilities Guide
Key: DERBY-429
URL: http://issues.apache.org/jira/browse/DERBY-429
Project: Derby
Type: Improvement
Components: Documentation
Versions: 10.2.0.0
Reporter: Mamta
It will be good to include synonyms on a table when dblook is run with -t
tablename option
--
Key: DERBY-430
URL: http://issues.apache.org/jira/browse/DERBY-430
Project: Derby
[ http://issues.apache.org/jira/browse/DERBY-380?page=all ]
Jeff Levitt updated DERBY-380:
--
Attachment: derby380.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-380?page=all ]
Andrew McIntyre resolved DERBY-380:
---
Resolution: Fixed
Committed, revision 208734. Additional comments should be attached to DERBY-425.
Doc Review (CLOSED TO FURTHER COMMENTS): Derby
[
http://issues.apache.org/jira/browse/DERBY-428?page=comments#action_12314877 ]
Bernt M. Johnsen commented on DERBY-428:
BTW: When the BatchUpdateException is thrown, the connection is closed down
(probably due to the
At Kathey's suggestion I took a short break from staring at auto-commit
code to turn my attention to some other issues. I change the following
items in the client code with this patch:
- Set password to a default value (defaultpassword)
- Set user to default to APP
- Set the default servername
Tests needed for verifying proper functioning of
ClientBaseDataSource.setConnectionAttributes() method
--
Key: DERBY-431
URL: http://issues.apache.org/jira/browse/DERBY-431
Currently, the Derby client contains a client-side implementation of
setQueryTimeout; using a TimerTask to invoke Statement.cancel() on the
client side. First of all, cancel() is not implemented, so this doesn't
work. Furthermore, we should use the server-side mechanism we now have
for
It says in section 15.2.2 of the document says:
next() — moves the cursor forward one row. Returns true if the cursor
is now
positioned on a row and false if the cursor is positioned after the last
row.
I guess the way to reconcile both this statement and the item in section
9.1 is for the
I have committed this patch with svn 208770.
Suresh Thalamati (JIRA) wrote:
[ 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
I am just getting back from J1 and I have a quite a few emails to wade
through. If/when you hace a cycle, if you can summarize the issues
outstanding, i can look at it and discuss with the EG. There are sooo
many emails from derby-dev, it is going to take me quite some time to
digest it all.
Minor code cleanup is needed in NetXAResource
--
Key: DERBY-433
URL: http://issues.apache.org/jira/browse/DERBY-433
Project: Derby
Type: Sub-task
Components: Network Client
Versions: 10.1.1.0, 10.2.0.0
[ http://issues.apache.org/jira/browse/DERBY-432?page=all ]
Kathey Marsden updated DERBY-432:
-
Component: Network Client
Client XA could still use code cleanup and testing
-
Key:
add jdbcapi/xaMorph.sql jdbcapi/xaJNDI jdbcapi/xaAnotherTest.sql to client xa
testing.
---
Key: DERBY-434
URL: http://issues.apache.org/jira/browse/DERBY-434
Project: Derby
Type:
jdbcapi/checkDataSource.java and jdbapi/checkDataSource30.java to tests should
be changed or extended to test client DataSources
-
Key: DERBY-435
[ http://issues.apache.org/jira/browse/DERBY-406?page=all ]
Philip Wilder updated DERBY-406:
Attachment: Derby406_409_410.patch
A Combined patch for DERBY-406, DERBY-409 and DERBY-410
#Warning#
When testing this patch there were locale (en_CA vs en_US)
Philip Wilder (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-406?page=all ]
Philip Wilder updated DERBY-406:
Attachment: Derby406_409_410.patch
A Combined patch for DERBY-406, DERBY-409 and DERBY-410
#Warning#
When testing this patch there
clean up imports and static field references in DRDA classes
-
Key: DERBY-436
URL: http://issues.apache.org/jira/browse/DERBY-436
Project: Derby
Type: Task
Components: Network Server
Versions:
This would only support setQueryTimeout() mechanism, but not the
cancel(), right? Wouldn't having support for cancel() be useful too, if
applications like to cancel a long running query? (that didn't have
timeout set) Also, I wonder if the protocol has support for cancel
mechanism If so, using
[EMAIL PROTECTED] wrote:
Currently, the Derby client contains a client-side implementation of
setQueryTimeout; using a TimerTask to invoke Statement.cancel() on the
client side. First of all, cancel() is not implemented, so this doesn't
work. Furthermore, we should use the server-side
[
http://issues.apache.org/jira/browse/DERBY-420?page=comments#action_12314908 ]
Andrew McIntyre commented on DERBY-420:
---
Merged to 10.1 branch with 208776
missing classes in published javadoc incorrect copyright date
The 10.1.1.0 bug list has a single entry left, DERBY-420:
http://issues.apache.org/jira/browse/DERBY-420
Dan, are there further javadoc modifications you would like to make?
As soon as this bug is closed I am planning on putting together a
release candidate for a vote.
For reference,
Philip Wilder wrote:
Kathey managed to spot some areas in which my patch could be improved
and some in which it was plain wrong. I'm still tidying up at the moment
but should hopefully have the Kathey approved patch in the near future.
Since this is open source it's useful to post the
Andrew McIntyre wrote:
The 10.1.1.0 bug list has a single entry left, DERBY-420:
http://issues.apache.org/jira/browse/DERBY-420
Dan, are there further javadoc modifications you would like to make? As
soon as this bug is closed I am planning on putting together a release
candidate for a
Philip Wilder (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-406?page=all ]
Philip Wilder updated DERBY-406:
Attachment: Derby406_409_410.patch
A Combined patch for DERBY-406, DERBY-409 and DERBY-410
So how is this patch different
[ http://issues.apache.org/jira/browse/DERBY-420?page=all ]
Daniel John Debrunner resolved DERBY-420:
-
Fix Version: 10.2.0.0
Resolution: Fixed
missing classes in published javadoc incorrect copyright date
[ http://issues.apache.org/jira/browse/DERBY-398?page=all ]
Deepa Remesh updated DERBY-398:
---
Attachment: derby-398_2.diff
derby-398_2.status
derbyall_report_2.txt
Hi Dan,
Thanks for looking into this patch. I have made the
Daniel John Debrunner wrote:
Since this is open source it's useful to post the feedback on patches to
the derby-dev list.
Hi Dan,
My comments were
- There should not be a default password set. Client should use
USER_ONLY_SECURITY by default if the password is not set and
SYSCS_UTIL.SYSCS_COMPRESS_TABLE does not work on tables that are created with
delimited identifier names.
---
Key: DERBY-437
URL:
[
http://issues.apache.org/jira/browse/DERBY-406?page=comments#action_12314924 ]
Kathey Marsden commented on DERBY-406:
--
I ran derbynetclientmatsand dataSourcePermissions_net.java under jcc for this
patch and all passed. The patch looks good to me,
TomohitoNakayama wrote:
I have found next implementation in
org.apache.derby.impl.jdbc.EmbedConnection#close().
/* Throw error to match DB2/JDBC if a tran is pending in
non-autocommit mode */
if (!autoCommit !transactionIsIdle()) {
throw
[ http://issues.apache.org/jira/browse/DERBY-438?page=all ]
A B updated DERBY-438:
--
Attachment: go.java
Attaching a repro for the problem. To run, just do java go.
Update triggers on tables with blob columns fail at execution time if the
Update triggers on tables with blob columns fail at execution time if the
triggered-SQL-statement references the blob column(s).
Key: DERBY-438
URL:
A B (JIRA) wrote:
Update triggers on tables with blob columns fail at execution time if the
triggered-SQL-statement references the blob column(s).
I'm suprised this is not documented, BLOB and CLOB columns do not work
with triggers. This is because within the database engine, there is no
Lance J. Andersen wrote:
I am just getting back from J1 and I have a quite a few emails to wade
through. If/when you hace a cycle, if you can summarize the issues
outstanding, i can look at it and discuss with the EG. There are sooo
many emails from derby-dev, it is going to take me quite
Daniel John Debrunner wrote:
I'm suprised this is not documented, BLOB and CLOB columns do not work
with triggers. This is because within the database engine, there is no
mechanism to create a java.sql.Blob object (or Clob) from a SQL BLOB
(CLOB) datatype. The java.sql.Blob returned from a
Army wrote:
Daniel John Debrunner wrote:
I'm suprised this is not documented, BLOB and CLOB columns do not work
with triggers. This is because within the database engine, there is no
mechanism to create a java.sql.Blob object (or Clob) from a SQL BLOB
(CLOB) datatype. The java.sql.Blob
Kathey Marsden wrote:
Lance J. Andersen wrote:
I am just getting back from J1 and I have a quite a few emails to wade
through. If/when you hace a cycle, if you can summarize the issues
outstanding, i can look at it and discuss with the EG. There are sooo
many emails from derby-dev, it is
Daniel John Debrunner wrote:
Army wrote:
1) Does this mean that we don't support _any_ triggers that are defined
on tables having lob columns? Or is there some qualifier to that?
Sorry, I think the qualifier should have been: accessing LOB columns of
the modified table by the action
41 matches
Mail list logo
