You'll have more chance of help if you make a self-contained reproducible
test. The test should create the table, populate the table, run the SELECT
+ UPDATE. Make sure to include your JDBC URL.
3 million rows shouldn't be necessary to reproduce the problem - it should
become apparent with much fewer rows.
On Tuesday, 8 December 2015 07:37:04 UTC+1, Dave Anonymous wrote:
>
> i tried an upgrade to 1.4 yesterday and had several problems.
> one of them is the speed. i have an update function which convert a column
> of ~3.000.000 rows. it took about 6 minutes to convert them with 1.3.176.
> with 1.4 after 14 hours 750.000 rows are converted (mv_store true or false
> makes no difference).
>
> the function is really easy (id is primary key, alarmdate has an index):
> try(PreparedStatement selectPstmt = cnctn.prepareStatement("SELECT ID,
> ALARMDATETEMP FROM ALARM_HISTORY;");){
> ResultSet result = selectPstmt.executeQuery();
> while(result.next()){
> byte[] alarmDate = result.getBytes("ALARMDATETEMP");
> Timestamp alarmDateStamp =
> this.convertByteToTimeStamp(alarmDate);
> try(PreparedStatement updatePstmt =
> cnctn.prepareStatement("UPDATE ALARM_HISTORY SET ALARMDATE=? WHERE ID=?;")){
> updatePstmt.setTimestamp(1, alarmDateStamp);
> updatePstmt.setInt(2, result.getInt("ID"));
> updatePstmt.executeUpdate();
> }
> }
> }.
>
>
>
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
