On 20/12/2012 14:12, Jean-Yves Linet wrote:
Hi,
May you could give more details about the structure of your table.
The table looks like this:
CREATE TABLE system_log (
id INTEGER GENERATED ALWAYS AS IDENTITY,
timeTIMESTAMP DEFAULT NULL,
usernameVARCHAR(15),
Do you have the same results if you exclude "details" field from your
columns list ?
2012/12/21 John English
> On 20/12/2012 14:12, Jean-Yves Linet wrote:
>
>> Hi,
>> May you could give more details about the structure of your table.
>>
>
> The table looks like this:
>
> CREATE TABLE system_lo
Pavel Bortnovskiy writes:
> Once in a while, I see the following errors. What may cause them?
>
> java.sql.SQLException: Container 1,329 not found.
The error means that one of the database files (table or index) cannot
be found. It typically happens because some DDL operation (for example
DROP I
Hi Knut
Thank you for your reply , but I still have some problems need your
help to answer.
*Question one**:
According to the reference manual:
About divider,the scale expressions: 31 - lp + ls - rs
the precision expressions: lp
Thank you, Knut, for your prompt response.
It seems that my caching of Prepared Statements is causing some problems.
In some previous responses, it was indicated that Derby is caching them
internally anyway, so maybe a better approach for me is not to cache them on my
side and create them anew?
On 21/12/2012 15:20, Jean-Yves Linet wrote:
Do you have the same results if you exclude "details" field from your columns
list ?
Yes. No significant change.
But: I'm trying it on my development system (127.0.0.1) since I can't play
around the live system, and the time varies by what other ap
In ij, I re-verify these statements and the results the same with you.
But I use java code using a JDBC connection Derby ,it will appear.
Can you help me explain the problem?
How are you displaying the result?
Are you using java.text.DecimalFormat?
If you are, what is y
On 21.12.2012 16:18, Pavel Bortnovskiy wrote:
Thank you, Knut, for your prompt response.
It seems that my caching of Prepared Statements is causing some problems.
In some previous responses, it was indicated that Derby is caching them
internally anyway, so maybe a better approach for me is not
I'm using an embedded driver with Derby in the in-memory only mode.
My application creates in-memory tables in Derby during its run, which are then
accessed by various components through JDBC.
-Original Message-
From: Kristian Waagan [mailto:kristian.waa...@oracle.com]
Sent: Friday, Decem
John English writes:
> On 20/12/2012 14:12, Jean-Yves Linet wrote:
>> Hi,
>> May you could give more details about the structure of your table.
>
> The table looks like this:
>
> CREATE TABLE system_log (
> id INTEGER GENERATED ALWAYS AS IDENTITY,
> timeTIMESTAMP DE
Pavel Bortnovskiy writes:
> Thank you, Knut, for your prompt response.
>
> It seems that my caching of Prepared Statements is causing some problems.
> In some previous responses, it was indicated that Derby is caching
> them internally anyway, so maybe a better approach for me is not to
> cache t
Knut, I'm running 10.9.1.0 and I can switch to the debug version of the
binaries, so that when such error occurs again (it's intermittent, rare, but it
does happen), I could give you a more full stack trace. I doubt, though, that I
would be able to create a standalone test program which reliably
12 matches
Mail list logo