agree! thx
On Fri, Sep 18, 2009 at 11:07 AM, Brett Wooldridge
wrote:
> Glad the updated statistics worked for you. The specificity of messageId
> seemed extremely high, and given only 1 million rows should have been
> returning sub-second results. You don't need indexes on either of the other
>
Glad the updated statistics worked for you. The specificity of messageId
seemed extremely high, and given only 1 million rows should have been
returning sub-second results. You don't need indexes on either of the other
two fields, they won't improve performance and will slow insertion speed.
Bret
Hey all,
Sorry been flat chat for a while, but I gotta say that the query
improved dramatically when the stats updated.
When I created the index, I didnt wait for the stats to be updated.
I came back the next day, and the query was running in sub seconds.
Now ExchangeSync can run well again on t
java.lang.StackOverflowError
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
at java.io.FilterInputStream.read(FilterInputStream.java:116)
at org.apache.derby.iapi.services.io.LimitInputStream.read(Unknown
...
That's a very interesting stack trace, thanks for includin
Thanks Bryan, I should have included the info from the derby.log. Here's
a small snippet of the ~1K lines from the log:
2009-09-17 14:58:48.873 GMT Thread[DRDAConnThread_19,5,derby.daemons]
(XID = 5212534), (SESSIONID = 21), (DATABASE = C:/temp/testDB), (DRDAID
= NF01.H0EE-4195946224626394
Hi Nilesh,
I'm not sure how the JDBC connection string you mentioned would have worked
for you.
As far as I'm aware, this is not supported by Derby - you should have gotten
an ERROR 08001: No suitable driver exception.
Maybe you are using a 3rd party product to achieve auto connection failover
a
Brett Wooldridge writes:
> You can force Derby to update statistics with this command:
>
> alter table compress [sequential]
>
> Note this command itself might take a long time -- dozens of minutes -- but in
> a system like yours you could get away with running it once or month or so at
> some o
"sarah.kho" writes:
> Hi
> Can someone pelase confirm that Derby can sort Arabic text correctly?
> I have a table and I can not get the data in correct order using the order
> by command.
Hi Sarah,
I cannot confirm that it works correctly with Arabic text, as I've never
tried, but I was under t
