I think what creates confusion here is that there is two different
uses of FOR UPDATE in SQL:
1. The standard DECLARE CURSOR ... FOR UPDATE which declares
updatability of a cursor. In JDBC, one will use ResultSets
instead of SQL Cursors and Connection.prepareStatement() allows
+1
I've tested the Object Innovations courseware with 10.1 on J2SDK
1.4.2_08 and JDK 1.5.0_03 on Windows XP. Tests were limited to student
labs. No problems were encountered except for Derby-231, but I've added
a for update clause for now. Hopefully a Derby-231 fix will make it
into 10.2.
+1
Kathey Marsden wrote:
Satheesh filed DERBY-310 to manage this issue, but to clarify
direction, I thought it worthwhile to submit this to vote:
There are some differences in behaviour when using the client vs the
embedded driver. Examples are DERBY-211 and DERBY-254. Other
differences
[
http://issues.apache.org/jira/browse/DERBY-197?page=comments#action_65605 ]
Edward Rayl commented on DERBY-197:
---
Escaping backslashes is unnecessay on Windows because it is not necessary to
use the backslash in the first place. Standard Java
I think any proposed changes should be invisible to the developer using
Derby. Therefore I think alternatives A or D make the most sense. I
would only choose D if the perceived benefit justifies it.
Ed
I would like to raise the issue of using 3rd party libraries with Derby.
For example, in
Is there a schedule for the release of the beta and release versions of
10.1?
Ed
Dag H. Wanvik (JIRA) wrote:
FOR UPDATE required for updatable result set to work
--
Key: DERBY-231
URL: http://issues.apache.org/jira/browse/DERBY-231
Project: Derby
Type: Improvement
Components: SQL
Versions:
Daniel John Debrunner wrote:
David Van Couvering wrote:
FYI, I couldn't 'get this to work even following this approach. I
finally had to copy the JDK14 and JDK13 directory trees to the default
location where ANT looks for them, and only then could I get it to work.
section at the bottom of
that page. I wonder if it might be possible to add Derby to the first
paragraph on that page as well, along with MySQL 3.22.9 and Oracle9i.
cheers,
-jean
Edward Rayl wrote:
I've just finished writing basic JDBC courseware for Object
Innovations that features Derby as its
Jean,
I noticed that the course description at
http://objectinnovations.com/CourseOutlines/168.html mentions Apache
Derby, but not until the System Requirements section at the bottom of
that page. I wonder if it might be possible to add Derby to the first
paragraph on that page as well, along
I've just finished writing basic JDBC courseware for Object Innovations
that features Derby as its default database. The course is geared
towards using the SQL standard rather than vendor proprietary SQL. The
same JDBC queries run against Derby, MySQL and Oracle. The announcement
is at:
Mamta Satoor wrote:
On Mon, 21 Feb 2005 11:58:36 -0800, Mamta Satoor [EMAIL PROTECTED] wrote:
Hi,
I have addressed the comments made by Dan for performance. Here is the
new patch. Let me know what you all think.
The comments made by Dan can be found in following thread
(commercial) and MySQL(open source). It would allow for easier
database and application migration. As for review... you don't really
want me doing that ;-)
Ed
Edward Rayl wrote:
I'm starting to wonder if this is on any of the reviewers' radar
screen. It's been two weeks
Andrew McIntyre wrote:
Recently, a vote was approved that the source for the Derby
documentation should be XML DITA format. Details can be found in
these threads:
http://mail-archives.eu.apache.org/mod_mbox/db-derby-dev/200502.mbox/
[EMAIL PROTECTED]
UNION DISTINCT? I thought
not, based on their documentation. They seem to have a MINUS, which may
map to EXCEPT.
Satheesh
Edward Rayl wrote:
Satheesh Bandaram wrote:
Take for example, the recently
added UNION/INTERSECT DISTINCT clause. This doesn't add any new
Please consider the JDocs web site as yet another alternative:
http://www.jdocs.com/
Kathey Marsden wrote:
I think it would be helpful to have links to both the published and
internal javadoc on the Derby website. I think the published javadoc
should be available off of the manuals page and
I would like to submit a patch for JDBC 2.0 Updatable Resultset apis -
delete functionality only. Please send in your vote based on the following
description and the attahced patch.
I for one would like to see these patches applied ASAP. I have a near
term need for updatable resultsets in
17 matches
Mail list logo
