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
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?
t;Bergquist, Brett"
>To: Derby Discussion
>Sent: Thursday, November 3, 2011 10:19 AM
>Subject: RE: SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE question
>
>Just a heads up, I have recently went through this exercise of having a table
>that is always being inserted at one end and del
Message-
From: Sundar Narayanaswamy [mailto:sundar...@yahoo.com]
Sent: Saturday, October 29, 2011 1:02 AM
To: derby-user@db.apache.org
Subject: Re: SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE question
I have posted the issue to DERBY-5487. I have also attached the Java test
program.
The test row
and/or in
> inplace compress. For your specific application would it work if
> inplace compress got table level locks during the purge phase?
>
--
View this message in context:
http://old.nabble.com/SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE-question-tp32736560p32757763.html
Sent from the Ap
I am thinking about this issue, thank you for reporting.
Sundar Narayanaswamy wrote:
I have posted the issue to DERBY-5487. I have also attached the Java test
program.
The test rows do insert at one end of the primary key and delete the other
end.. Interestingly, I noticed that primary key sp
ew this message in context:
http://old.nabble.com/SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE-question-tp32736560p32742387.html
Sent from the Apache Derby Users mailing list archive at Nabble.com.
Posting your test to a JIRA issue would be best. It would be
interesting to post the space table results after each
insert/delete/compress iteration (or every 10, ...).
When do you commit (every row or every 1)? Is it multi-threaded?
Does your
test always insert rows at one end of the ind
On 10/27/2011 09:26 PM, Sundar Narayanaswamy wrote:
I insert 1 rows into the table, then delete all that rows. I then call
SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE
with just the option to purge rows so that the space left behind by deleted
rows can be reused for future inserts. I have
the in
Hi,
I am trying to use Derby database in the embedded mode in an application. I
wrote a test program where I have a
table (named LOCATION) with 4 columns as below:create table location(id int,
num int, addr varchar(40), zip int, primary key(id, zip))
create index loc_index on location (num)
I
10 matches
Mail list logo
