Hi Cimballi,
On 03-03-2009 08:17:06 -0500, Cimballi wrote:
> When the file is small (up to 2 Mo, around 15 000 items), no problem.
> If the file is bigger (20 Mo, around 100 000 items), then at a moment
> the select next value return null.
> Here is the java.sql log :
>
> 2009-03-02 21:14:30,324 | DEBUG | java.sql.Connection
> | debug | {conn-170420} Connection
> 2009-03-02 21:14:30,324 | DEBUG | java.sql.Connection
> | debug | {conn-170420} Preparing Statement: SELECT NEXT
> VALUE FOR seq_oasis_report_data_id
> 2009-03-02 21:14:30,334 | DEBUG | java.sql.PreparedStatement |
> debug | {pstm-170421} Executing Statement: SELECT NEXT
You seem to use prepared statements and executes of them to do this. Is
there an intermediate commit in your application, by chance? If your
prepared statements were created in an (explicit) transaction, the
prepared statement gets lost after the commit. It is a bug that this is
returned as a NULL, though.
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Monetdb-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-developers
