I observed this error a few times during some experiments I did some
time ago. See DERBY-637. Not the same setting, though. Client/server,
30 GB database. When this started to occur, all my transaction fail
with this error. Restarting the database, made the error disappear.
--
Øystein
What David wants, is the feature rgistered in
https://issues.apache.org/jira/browse/DERBY-581
Craig L Russell wrote (2007-05-13 12:06:38):
Also, how is maxrows related to the fetch size of a ResultSet?
As I understand it, the fetch size relates to the number of rows
returned by the server
Hi,
I am using Derby in Network mode with a webapp in Tomcat. I start it through
an ApplicationListener and I shut it down when I stop the webapp. I have
defined a JNDI Datasource with a dbcp pool to the server in my context.xml
file.
All seems to be going fine but when I shutdown my webapp, the
Hi Mike,
I am using different connections to do my load and select. I do my bulk
load into an empty table.
Thanks
Patty
-Original Message-
From: Mike Matrigali [mailto:[EMAIL PROTECTED]
Sent: Friday, May 11, 2007 8:06 PM
To: Derby Discussion
Subject: Re: SQL Exception: Container xxx
ehsavoie wrote:
Hi,
I am using Derby in Network mode with a webapp in Tomcat. I start it
through an ApplicationListener and I shut it down when I stop the webapp.
I have defined a JNDI Datasource with a dbcp pool to the server in my
context.xml file.
All seems to be going fine but when
All seems to be going fine but when I shutdown my webapp, the
NetworkServerControl.shutdown() is correctly called but I have db.lck and
dbex.lck left :o(.
I think this may be DERBY-51:
http://issues.apache.org/jira/browse/DERBY-51
Also if I try to restart my webapp, the
Bryan Pendleton wrote:
All seems to be going fine but when I shutdown my webapp, the
NetworkServerControl.shutdown() is correctly called but I have db.lck and
dbex.lck left :o(.
I think this may be DERBY-51:
http://issues.apache.org/jira/browse/DERBY-51
Also if I try to restart my
Bryan Pendleton wrote:
shutdown command fails if I try it through a network url (database not
found) or with an embeded url (java.sql.SQLTransientConnectionException:
Database 'ed' shutdown.)
I don't know about the database not found part, but the shutdown command
always throws an
ehsavoie wrote:
Bryan Pendleton wrote:
All seems to be going fine but when I shutdown my webapp, the
NetworkServerControl.shutdown() is correctly called but I have db.lck
and
dbex.lck left :o(.
I think this may be DERBY-51:
http://issues.apache.org/jira/browse/DERBY-51
Also
shutdown command fails if I try it through a network url (database not
found) or with an embeded url (java.sql.SQLTransientConnectionException:
Database 'ed' shutdown.)
I don't know about the database not found part, but the shutdown command
always throws an exception, so getting Database 'ed'
While I was trying to delete tables through Execute command screen of
Netbeans, I got an error message saying
The coglomerate (27265) requested does not exist.
--
View this message in context:
http://www.nabble.com/can%27t-delete-table-tf3754439.html#a10610657
Sent from the Apache Derby Users
David Van Couvering wrote (2007-05-14 09:13:28):
OK, so do I have it right that the right way to hint to the driver
to not cache all one million rows when I only need ten rows is to use
setMaxRows()?
No. setFetchSize() is an optimization hint, setMaxRows() is a limit on
the ResultSet size. A
Thanks for the tip, Bernt, but I must humbly say yuck! to the syntax.
OK, getting over that, it's pretty worthless to me given that Derby
doesn't use it and Derby is the primary DB used by NetBeans. But
let's say it was implemented -- would it work with a result set that
is a join across
Also, there are not a lot of DBs that support that syntax... :-(
David Van Couvering wrote:
Thanks for the tip, Bernt, but I must humbly say yuck! to the syntax.
OK, getting over that, it's pretty worthless to me given that Derby
doesn't use it and Derby is the primary DB used by NetBeans.
David Van Couvering wrote (2007-05-14 13:11:00):
Thanks for the tip, Bernt, but I must humbly say yuck! to the syntax.
OK, getting over that, it's pretty worthless to me given that Derby
doesn't use it and Derby is the primary DB used by NetBeans. But
let's say it was implemented -- would
Lance J. Andersen wrote (2007-05-14 16:38:03):
Also, there are not a lot of DBs that support that syntax... :-(
As far as I know, it's supported by DB2, MSSQL and Oracle (not quite
pretty close anyway). MySQL and PostgreSQL has this non-standard
LIMIT/OFFSET stuff.
--
Bernt Marius Johnsen,
Right but most if not all RDBMS support a form of LIMIT. It may be non
standard but support is there.
On 5/14/07, Lance J. Andersen [EMAIL PROTECTED] wrote:
Also, there are not a lot of DBs that support that syntax... :-(
David Van Couvering wrote:
Thanks for the tip, Bernt, but I must
You can add MS SQL-Server and Sybase, as well as some more RDBMS. This is a
feature that is required a lot by IDE's, since they need to manipulate data
and metadata a lot more than other types of client applications...
On 5/14/07, Bernt M. Johnsen [EMAIL PROTECTED] wrote:
Lance J. Andersen
yes, most databases have a way to do that, my point was that the syntax
below is not portable... so the driver via setmaxrows() should address that.
Francois Orsini wrote:
Right but most if not all RDBMS support a form of LIMIT. It may be non
standard but support is there.
On 5/14/07, *Lance
I thought it would not as it is bound to the resultset (client-side) versus
actual processing on the database engine side. I mean, if I only want the
first 10 rows that qualifies some query, I don't want to have 1 million rows
returned from the database engine (e.g. server) as part of my
Most drivers try and let the server side handle this so what gets passed
across the wire is the rows that meet the specified limit. This is what
we did in jConnect for example.
When this limit actually occurs could depend on how the backend applies
it and the type of query (for example if
How are you accessing Netbeans from Netbeans? in Embedded or Client-Server
mode? You might want to check derby.log file to see if there is any
stacktrace(s) relevant to this error...Also, are you by any chance accessing
the same database from some other Derby instance? there should be a lock
file
Cool, would love to know how and what kind of hint is passed to the database
engine - well, as far as Derby is concerned, setMaxRows() does not affect
the DB engine, unless I'm mistaken - Now as far as using SQL LIMIT WITH
OFFSET, it is up to the database engine to try and restrict the number of
-Original Message-
From: Bryan Pendleton [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 9:58 AM
To: Derby Discussion
Subject: Re: Executing command from a file via JDBC
I didn't want to distribute derbytools.jar with my application. I guess
was looking for something
P.S. As you can see, the code is pretty basic... surely there are other
aspects of the Derby SQL syntax (besides comments and quotes) that aren't
even considered. It would be cool if Derby exposed a similar utility method
which depended directly on Derby's internal parser, so that it would be
Jim Newsham wrote:
-Original Message-
From: Bryan Pendleton [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 10, 2007 9:58 AM
To: Derby Discussion
Subject: Re: Executing command from a file via JDBC
I didn't want to distribute derbytools.jar with my application. I guess
was looking for
Yes something like that. ;) However, I would expect such a method to throw
an exception the first time an error occurs. I don't see the purpose of
blindly continuing in the face of errors.
It was some time ago, so I don't recall if I didn't use this method because
it didn't exist at the
27 matches
Mail list logo
