Is it unusual that Derby (used in-memory only) seems to throw an out of memory
exception when executing 180,000 batched insert statements?
(The JVM was started with -Xms1024m -Xmx2048m):
Caused by: java.sql.SQLException: Java exception: 'GC overhead limit exceeded:
java.lang.OutOfMemoryError'.
Hi,
Derby does support UDTs. One can use any java.io.Serializable java class as a
UDT.
On the other hand, derby does not support SQL ARRAY types.
However, every java array is an object that implements java.io.Serializable,
so can one define a UTD of the form
CREATE TYPE APP.DARRAY
EXT
David Zanter wrote:
The worst case for Derby would be a data distribution of an index which
resulted in one row on each leaf.
By this are you meaning that any "CREATE UNIQUE INDEX" would be worse
case scenario?
no, what I am referring to is the data distribution in the index of
insert
ate/time as integers as:
>
> Time HHmmss: 103152
>
> Date MMdd: 2008
>
> I could get as far as:
>
> *cast*(*current_time as **VARCHAR*(8)),
>
> *cast*(*current_date as **VARCHAR*(10)),
>
> but I was unable to find a function similar to str_replace in Syba
Date MMdd: 20111108
I could get as far as:
*cast*(*current_time as **VARCHAR*(8)),
*cast*(*current_date as **VARCHAR*(10)),
but I was unable to find a function similar to str_replace in Sybase
to remove “:” and “-“
Thank you,
Pavel.
Jefferies archives and monitors outgoing and incom
Hello:
Are there Derby built-in functions which can allow me to extract current
date/time as integers as:
Time HHmmss: 103152
Date MMdd: 2008
I could get as far as:
cast(current_time as VARCHAR(8)),
cast(current_date as VARCHAR(10)),
but I was
