Hi Michael,
I was afraid that you might have missed some context in this thread.
Bernt M. Johnsen wrote (2006-03-01 10:27:57):
To be precise:
You may not call setObject("middle_name", null), but you may call
one of the following
setObject("middle_name", null, java.sql.Types.VARCHAR)
or
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 03, 2006 5:47 PM
> To: Derby Discussion
> Subject: Re: SQL Exception
>
> Hi Michael,
>
> Nice to see you're back.
>
> On Mar 3, 2006, at 10:15 AM, Michael Segel wrote:
>
> > On Wednesday 01
On 3/3/06, Rick Hillegas <[EMAIL PROTECTED]> wrote:
>
> For instance, when I try to build the postscript version of the
> Developer's guide (ant -quiet pdf.devguide), I get a directory
> (out/devguide) with a derbydev.fo file and several gifs. But no .pdf file.
>
> Would appreciate advice on what I
I am having trouble generating the postscript versions of most of our
user docs. I can generate html and monohtml versions for all user
guides. I can also generate postscript versions of the Reference and
Tuning guides. However, I'm having trouble generating postscript
versions of the other doc
Hi Michael,
Nice to see you're back.
On Mar 3, 2006, at 10:15 AM, Michael Segel wrote:
On Wednesday 01 March 2006 1:40 pm, you wrote:
Sigh.
I kind of avoided this discussion because I was busy giving a
presentation on
Database Security to the local DB2/Informix user group(s).
null = a null
Mike,
Thanks for your suggestions. I think I am going to try to rewrite some sections
of code to pass the database connection in the constructor as it seems to make
sense for my application to do this (as some classes will be created and
destroyed many times).
I'm not convinced it's due to sco
On Friday 03 March 2006 9:41 am, Rhys Campbell wrote:
> Initially I was doing it the start of each class and reusing the same
> connection variable. But Derby seemed to auto-close the connection after
> each statement.
>
Uhmm. No. Derby shouldn't be doing an auto-close after each connection.
I thin
Initially I was doing it the start of each class and reusing the same
connection variable. But Derby seemed to auto-close the connection after
each statement.
I was burning the midnight oil on it last night. I realize it's not the
most efficient way of doing things, but wouldn't this eliminate pro
On Friday 03 March 2006 7:58 am, Rhys Campbell wrote:
> Hi,
>
> I have a method called initDatabase() which returns the Connection
> variable. When I execute any query against the database I call another
> method of which the first parameter is the Connection (i.e. I place
> initDatabase() as the p
Hi,
I have a method called initDatabase() which returns the Connection
variable. When I execute any query against the database I call another
method of which the first parameter is the Connection (i.e. I place
initDatabase() as the parameter.
i.e. ResultSet rs = database.executeQuery(initDatabas
On Friday 03 March 2006 3:17 am, Rhys Campbell wrote:
> Hi Rajesh,
>
>
>
> I can post some code later when I return from work. My app is written
> using Java and uses a single table Derby database. At present this only
> has three records in it. I did try to completely shutdown Derby at the
> end o
On Friday 03 March 2006 5:04 am, Thomas Vatter wrote:
> I have shutdown derby, dropped the database by removing its folder,
> started derby (no large memory consuming, stays low), recreated
> the database, imported 1300 data and showed them in my application.
> Memory stays low, but the ordering is
Thomas Vatter wrote:
The result of distributing application and database over two machines is:
Import of the critical data now works, no hanging at 1200 records
(I need to start derby with -Xmx1024m else an outofmemory exception
is thrown). My import algorithm has to be reviewed, it allocates
m
I have shutdown derby, dropped the database by removing its folder,
started derby (no large memory consuming, stays low), recreated
the database, imported 1300 data and showed them in my application.
Memory stays low, but the ordering is not ok. This is a mystery for me.
Hi Rajesh,
I can post some code later when I return
from work. My app is written using Java and uses a single table Derby database. At
present this only has three records in it. I did try to completely shutdown Derby at the end of one
class before restarting it in the class that had the
The result of distributing application and database over two machines is:
Import of the critical data now works, no hanging at 1200 records
(I need to start derby with -Xmx1024m else an outofmemory exception
is thrown). My import algorithm has to be reviewed, it allocates
memory in a loop, 100mb w
16 matches
Mail list logo
