Re: [h2] Row not found when trying to delete from index [v1.3.174]
Hi, This issue is very consistently happening when the process is close to > using its heap limit. Perhaps there is some OutOfMemory error being > suppressed? > That could be. Do you have a simple, reproducible test case? Could you try with version 1.4.x? Regards, Thomas > > On Thursday, May 22, 2014 11:45:20 AM UTC-4, Thomas Mueller wrote: >> >> Hi, >> >> You could export the database to a script file, and then create a new >> database from that. >> >> Regards, Thomas >> >> On Wednesday, May 21, 2014, Sander Sõnajalg >> wrote: >> >>> Hi, >>> >>> so this is basically a known issue? And as I understand from your >>> context, you are currently lacking a test case that would reproduce the >>> issue? I can't provide one at the moment either, as I can't acquire the >>> customer's database that reproduces this (and it doesn't occur in our own >>> environment). But sooner or later I might also be able to get a database >>> instance that is affected by this.. should I then convert it into a ticket >>> and provide a test case? >>> >>> Anyhow, maybe you have some recommendations about what to try to resolve >>> this..? Dropping and recreating the index probably doesn't provide a final >>> solution, as i read from other threads. >>> >>> Thanks! >>> Sander. >>> >>> >>> >>> > > I'm afraid MVCC is still experimental in that release. It works for > some people, but not for everybody. > > I know this is no help, but regarding the experimental options, I have > seen -- >>> 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. >>> >> -- > 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. > -- 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.
Re: [h2] Row not found when trying to delete from index [v1.3.174]
This issue is very consistently happening when the process is close to using its heap limit. Perhaps there is some OutOfMemory error being suppressed? On Thursday, May 22, 2014 11:45:20 AM UTC-4, Thomas Mueller wrote: > > Hi, > > You could export the database to a script file, and then create a new > database from that. > > Regards, Thomas > > On Wednesday, May 21, 2014, Sander Sõnajalg > > > wrote: > >> Hi, >> >> so this is basically a known issue? And as I understand from your >> context, you are currently lacking a test case that would reproduce the >> issue? I can't provide one at the moment either, as I can't acquire the >> customer's database that reproduces this (and it doesn't occur in our own >> environment). But sooner or later I might also be able to get a database >> instance that is affected by this.. should I then convert it into a ticket >> and provide a test case? >> >> Anyhow, maybe you have some recommendations about what to try to resolve >> this..? Dropping and recreating the index probably doesn't provide a final >> solution, as i read from other threads. >> >> Thanks! >> Sander. >> >> >> >> I'm afraid MVCC is still experimental in that release. It works for some people, but not for everybody. I know this is no help, but regarding the experimental options, I have seen >>> >>> -- >> 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. >> > -- 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.
Re: [h2] Row not found when trying to delete from index [v1.3.174]
Hi, You could export the database to a script file, and then create a new database from that. Regards, Thomas On Wednesday, May 21, 2014, Sander Sõnajalg wrote: > Hi, > > so this is basically a known issue? And as I understand from your context, > you are currently lacking a test case that would reproduce the issue? I > can't provide one at the moment either, as I can't acquire the customer's > database that reproduces this (and it doesn't occur in our own > environment). But sooner or later I might also be able to get a database > instance that is affected by this.. should I then convert it into a ticket > and provide a test case? > > Anyhow, maybe you have some recommendations about what to try to resolve > this..? Dropping and recreating the index probably doesn't provide a final > solution, as i read from other threads. > > Thanks! > Sander. > > > > >>> >>> I'm afraid MVCC is still experimental in that release. It works for >>> some people, but not for everybody. >>> >>> I know this is no help, but regarding the experimental options, I have >>> seen >> >> -- > 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. > -- 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.
Re: [h2] Row not found when trying to delete from index [v1.3.174]
Hi, so this is basically a known issue? And as I understand from your context, you are currently lacking a test case that would reproduce the issue? I can't provide one at the moment either, as I can't acquire the customer's database that reproduces this (and it doesn't occur in our own environment). But sooner or later I might also be able to get a database instance that is affected by this.. should I then convert it into a ticket and provide a test case? Anyhow, maybe you have some recommendations about what to try to resolve this..? Dropping and recreating the index probably doesn't provide a final solution, as i read from other threads. Thanks! Sander. >> >> I'm afraid MVCC is still experimental in that release. It works for >> some people, but not for everybody. >> >> I know this is no help, but regarding the experimental options, I have >> seen > > -- 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.
Re: [h2] Row not found when trying to delete from index [v1.3.174]
Am Dienstag, 20. Mai 2014 20:00:44 UTC+2 schrieb Noel Grandin: > > On Tue, May 20, 2014 at 6:50 PM, > > wrote: > > > > We are on version 1.3.172, with connection string > > "jdbc:h2:./data/db/db;MVCC=TRUE;MAX_COMPACT_TIME=6000;" -- so no > > experimental flags or anything in my case. > > > > I'm afraid MVCC is still experimental in that release. It works for > some people, but not for everybody. > > I know this is no help, but regarding the experimental options, I have > seen this Exception in customer's logs every now and then since using H2, > even with no additional options at all. > -- 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.
Re: [h2] Row not found when trying to delete from index [v1.3.174]
On Tue, May 20, 2014 at 6:50 PM, wrote: > > We are on version 1.3.172, with connection string > "jdbc:h2:./data/db/db;MVCC=TRUE;MAX_COMPACT_TIME=6000;" -- so no > experimental flags or anything in my case. > I'm afraid MVCC is still experimental in that release. It works for some people, but not for everybody. > It would also be very helpful if somebody could take 5 minutes to explain a > bit what this exceptions substantially means... why shouldn't it not be able If we knew what it was, we'd fix it. -- 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.
Re: [h2] Row not found when trying to delete from index [v1.3.174]
+1 to this topic. We are on version 1.3.172, with connection string " jdbc:h2:./data/db/db;MVCC=TRUE;MAX_COMPACT_TIME=6000;" -- so no experimental flags or anything in my case. One of our customers consistently produces "Row not found when trying to delete from index" on 2 tables. Here are the exceptions: In table "lease" javax.persistence.PersistenceException: org.h2.jdbc.JdbcSQLException: Row not found when trying to delete from index "PUBLIC.I_LEASE_CREATED_AT_UPDATED_AT_TOKEN_ID: ( /* key:14162 */ 14162, 42, 101, FALSE, TIMESTAMP '2013-11-03 01:14:30.302', TIMESTAMP '2013-11-03 01:44:28.159', TIMESTAMP '2013-11-03 01:44:28.159', TRUE, NULL, NULL, -2318)"; SQL statement: DELETE FROM lease WHERE expired = 1 AND updated_at < ? LIMIT 1 [90112-172] at com.avaje.ebeaninternal.server.persist.ExeUpdateSql.execute(ExeUpdateSql.java:76) ~[license-server.jar:2.2.1] at com.avaje.ebeaninternal.server.persist.DefaultPersistExecute.executeSqlUpdate(DefaultPersistExecute.java:115) ~[license-server.jar:2.2.1] at com.avaje.ebeaninternal.server.core.PersistRequestUpdateSql.executeNow(PersistRequestUpdateSql.java:44) ~[license-server.jar:2.2.1] at com.avaje.ebeaninternal.server.core.PersistRequest.executeStatement(PersistRequest.java:74) ~[license-server.jar:2.2.1] at com.avaje.ebeaninternal.server.core.PersistRequestUpdateSql.executeOrQueue(PersistRequestUpdateSql.java:49) ~[license-server.jar:2.2.1] at com.avaje.ebeaninternal.server.persist.DefaultPersister.executeSqlUpdate(DefaultPersister.java:139) ~[license-server.jar:2.2.1] Caused by: org.h2.jdbc.JdbcSQLException: Row not found when trying to delete from index "PUBLIC.I_LEASE_CREATED_AT_UPDATED_AT_TOKEN_ID: ( /* key:14162 */ 14162, 42, 101, FALSE, TIMESTAMP '2013-11-03 01:14:30.302', TIMESTAMP '2013-11-03 01:44:28.159', TIMESTAMP '2013-11-03 01:44:28.159', TRUE, NULL, NULL, -2318)"; SQL statement: DELETE FROM lease WHERE expired = 1 AND updated_at < ? LIMIT 1 [90112-172] at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) ~[license-server.jar:2.2.1] at org.h2.message.DbException.get(DbException.java:169) ~[license-server.jar:2.2.1] at org.h2.message.DbException.get(DbException.java:146) ~[license-server.jar:2.2.1] at org.h2.index.PageBtreeLeaf.remove(PageBtreeLeaf.java:230) ~[license-server.jar:2.2.1] at org.h2.index.PageBtreeNode.remove(PageBtreeNode.java:332) ~[license-server.jar:2.2.1] at org.h2.index.PageBtreeNode.remove(PageBtreeNode.java:332) ~[license-server.jar:2.2.1] The index definition for this table (copy-pasting liquibase XML) : In table "access_token" Caused by: org.h2.jdbc.JdbcSQLException: Row not found when trying to delete from index "PUBLIC.I_SEATS_SAMPLE_CREATED_AT: ( /* key:5057781 */ 5057781, TIMESTAMP '2013-11-03 01:11:00.0', 2, 49, 12)"; SQL statement: delete from access_token where id=? and name=? and auth_token=? and subnet_mask=? and max_users is null and is_active=? and is_total_token=? and created_at=? [90112-172] at org.h2.message.DbException.getJdbcSQLException(DbException.java:329) ~[license-server.jar:2.2.1] at org.h2.message.DbException.get(DbException.java:169) ~[license-server.jar:2.2.1] at org.h2.message.DbException.get(DbException.java:146) ~[license-server.jar:2.2.1] at org.h2.index.PageBtreeLeaf.remove(PageBtreeLeaf.java:230) ~[license-server.jar:2.2.1] at org.h2.index.PageBtreeNode.remove(PageBtreeNode.java:332) ~[license-server.jar:2.2.1] at org.h2.index.PageBtreeNode.remove(PageBtreeNode.java:332) ~[license-server.jar:2.2.1] Here's the index definition for seats_sample table that looks to fail: ... and here's the foreign key constraint that connects them and defines the on-delete action, just in case: The first of those indexes is a multi-column indexes which i doubt that even "works"... if I investivate see my queries with EXPLAIN, they mostly don't seem to be used at all (although the columns I query by are exactly the same). Thus, for at least one of the cases above, the solution for me is probably to get rid of the multi-column index for good. But anyhow, I still wanted to raise this here.. there might be some underlying root cause that maybe could be improved. It would also be very helpful if somebody could take 5 minutes to explain a bit what this exceptions substantially means... why shouldn't it not be able to delete from index? Is the index itself corrupt then, or could it be some sort of an issue in H2 code? This does not reproduce consinstently, i.e. it happens for our customer (whose database actually doesn't look to be corrupt, i.e. application itself works), but we ourselves cannot reproduce it. Makes me wonder Thanks! Sander. -- 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...@goo
Re: [h2] Row not found when trying to delete from index [v1.3.174]
MULTI_THREADED is still a little experimental for now. I would suggest disabling that for now if you are experiencing DB corruption, unless you are willing to create reproducible test-cases for us to look at :-) On 2013-12-14 13:56, Michael Descher wrote: jdbc:h2:file:/some/path/h2/MyTunesRSS;MAX_LOG_SIZE=64;MULTI_THREADED=1 -- 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/groups/opt_out.
Re: [h2] Row not found when trying to delete from index [v1.3.174]
By the way, I received more log files from my customer and it seems the exception shows the same index row each time he runs the problematic update. Michael -- 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/groups/opt_out.
Re: [h2] Row not found when trying to delete from index [v1.3.174]
Hi Thomas, the URL is jdbc:h2:file:/some/path/h2/MyTunesRSS;MAX_LOG_SIZE=64;MULTI_THREADED=1 Regards Michael -- 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/groups/opt_out.
Re: [h2] Row not found when trying to delete from index [v1.3.174]
Hi, Could you tell me what database URL you are using? Currently, when a row is updated, I believe all indexes are modified. I understand this is not needed here, and changing it would improve performance. Regards, Thomas On Wed, Dec 11, 2013 at 1:03 PM, Michael Descher wrote: > 2013-12-10 13:38:09,978 [pool-1-thread-1] ERROR > de.codewave.mytunesrss.webadmin.ContentConfigPanel - Could not rename > genres. > org.h2.jdbc.JdbcSQLException: Çàïèñü íå íàéäåíà ïðè óäàëåíèè èç èíäåêñà > "PUBLIC.IDX_TRACK_LOWER_ALBUM_ARTIST: ( /* key:35419 */ > 'file_4087a0b736d9866abc220a7736d686b7c7a876b2', 'Just a Lil Bit of > History', 'just a lil bit of history', 'L-Boy-N-Boo Loc', 'l-boy-n-boo > loc', 'L-Boy-N-Boo Loc', 'l-boy-n-boo loc', 'Just A Lil'' Bit of History', > 'just a lil'' bit of history', 193, 1, > 'H:\MP3\2004\L-Boy-N-Boo_Loc-Just_A_Lil_Bit_of_History-2004-CR\01-l-boy-n-boo_loc-just_a_lil_bit_of_history-cr.mp3', > 'mp3', FALSE, 'Audio', 'FileSystem', > 'a9aab034-0a8e-472d-8ae3-4cbbacfaa74f', 'Rap', 'rap', 'Rap', NULL, NULL, > 1385989685310, 0, 0, NULL, 0, 0, NULL, 2004, NULL, NULL, NULL, 0, 0, NULL, > 0)" > Row not found when trying to delete from index > "PUBLIC.IDX_TRACK_LOWER_ALBUM_ARTIST: ( /* key:35419 */ > 'file_4087a0b736d9866abc220a7736d686b7c7a876b2', 'Just a Lil Bit of > History', 'just a lil bit of history', 'L-Boy-N-Boo Loc', 'l-boy-n-boo > loc', 'L-Boy-N-Boo Loc', 'l-boy-n-boo loc', 'Just A Lil'' Bit of History', > 'just a lil'' bit of history', 193, 1, > 'H:\MP3\2004\L-Boy-N-Boo_Loc-Just_A_Lil_Bit_of_History-2004-CR\01-l-boy-n-boo_loc-just_a_lil_bit_of_history-cr.mp3', > 'mp3', FALSE, 'Audio', 'FileSystem', > 'a9aab034-0a8e-472d-8ae3-4cbbacfaa74f', 'Rap', 'rap', 'Rap', NULL, NULL, > 1385989685310, 0, 0, NULL, 0, 0, NULL, 2004, NULL, NULL, NULL, 0, 0, NULL, > 0)"; SQL statement: > UPDATE track SET genre = original_genre, lower_genre = > LOWER(original_genre) [90112-174] > at > org.h2.message.DbException.getJdbcSQLException(DbException.java:332) > at org.h2.message.DbException.get(DbException.java:172) > at org.h2.message.DbException.get(DbException.java:149) > at org.h2.index.PageBtreeLeaf.remove(PageBtreeLeaf.java:230) > at org.h2.index.PageBtreeNode.remove(PageBtreeNode.java:332) > at org.h2.index.PageBtreeNode.remove(PageBtreeNode.java:332) > at org.h2.index.PageBtreeNode.remove(PageBtreeNode.java:332) > at org.h2.index.PageBtreeIndex.remove(PageBtreeIndex.java:239) > at org.h2.table.RegularTable.removeRow(RegularTable.java:376) > at org.h2.table.Table.updateRows(Table.java:449) > at org.h2.command.dml.Update.update(Update.java:144) > at org.h2.command.CommandContainer.update(CommandContainer.java:79) > at org.h2.command.Command.executeUpdate(Command.java:253) > at > org.h2.jdbc.JdbcPreparedStatement.execute(JdbcPreparedStatement.java:193) > > What I don't understand at first glance is the reason for deleting > anything from that index. The index is on a single column of the modifed > table but it is not used in the update statement that causes the deletion. > What the update does is copy the original_genre column into two other > columns (genre and lower_genre) of the same table. Background for the > use-case, the original_genre column holds the original value while genre > and lower_genre hold a possibly modified value. This update statement is > for the use-case of resetting the possibly modified values to their > original ones. > > -- > 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/groups/opt_out. > -- 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/groups/opt_out.
[h2] Row not found when trying to delete from index [v1.3.174]
2013-12-10 13:38:09,978 [pool-1-thread-1] ERROR de.codewave.mytunesrss.webadmin.ContentConfigPanel - Could not rename genres. org.h2.jdbc.JdbcSQLException: Çàïèñü íå íàéäåíà ïðè óäàëåíèè èç èíäåêñà "PUBLIC.IDX_TRACK_LOWER_ALBUM_ARTIST: ( /* key:35419 */ 'file_4087a0b736d9866abc220a7736d686b7c7a876b2', 'Just a Lil Bit of History', 'just a lil bit of history', 'L-Boy-N-Boo Loc', 'l-boy-n-boo loc', 'L-Boy-N-Boo Loc', 'l-boy-n-boo loc', 'Just A Lil'' Bit of History', 'just a lil'' bit of history', 193, 1, 'H:\MP3\2004\L-Boy-N-Boo_Loc-Just_A_Lil_Bit_of_History-2004-CR\01-l-boy-n-boo_loc-just_a_lil_bit_of_history-cr.mp3', 'mp3', FALSE, 'Audio', 'FileSystem', 'a9aab034-0a8e-472d-8ae3-4cbbacfaa74f', 'Rap', 'rap', 'Rap', NULL, NULL, 1385989685310, 0, 0, NULL, 0, 0, NULL, 2004, NULL, NULL, NULL, 0, 0, NULL, 0)" Row not found when trying to delete from index "PUBLIC.IDX_TRACK_LOWER_ALBUM_ARTIST: ( /* key:35419 */ 'file_4087a0b736d9866abc220a7736d686b7c7a876b2', 'Just a Lil Bit of History', 'just a lil bit of history', 'L-Boy-N-Boo Loc', 'l-boy-n-boo loc', 'L-Boy-N-Boo Loc', 'l-boy-n-boo loc', 'Just A Lil'' Bit of History', 'just a lil'' bit of history', 193, 1, 'H:\MP3\2004\L-Boy-N-Boo_Loc-Just_A_Lil_Bit_of_History-2004-CR\01-l-boy-n-boo_loc-just_a_lil_bit_of_history-cr.mp3', 'mp3', FALSE, 'Audio', 'FileSystem', 'a9aab034-0a8e-472d-8ae3-4cbbacfaa74f', 'Rap', 'rap', 'Rap', NULL, NULL, 1385989685310, 0, 0, NULL, 0, 0, NULL, 2004, NULL, NULL, NULL, 0, 0, NULL, 0)"; SQL statement: UPDATE track SET genre = original_genre, lower_genre = LOWER(original_genre) [90112-174] at org.h2.message.DbException.getJdbcSQLException(DbException.java:332) at org.h2.message.DbException.get(DbException.java:172) at org.h2.message.DbException.get(DbException.java:149) at org.h2.index.PageBtreeLeaf.remove(PageBtreeLeaf.java:230) at org.h2.index.PageBtreeNode.remove(PageBtreeNode.java:332) at org.h2.index.PageBtreeNode.remove(PageBtreeNode.java:332) at org.h2.index.PageBtreeNode.remove(PageBtreeNode.java:332) at org.h2.index.PageBtreeIndex.remove(PageBtreeIndex.java:239) at org.h2.table.RegularTable.removeRow(RegularTable.java:376) at org.h2.table.Table.updateRows(Table.java:449) at org.h2.command.dml.Update.update(Update.java:144) at org.h2.command.CommandContainer.update(CommandContainer.java:79) at org.h2.command.Command.executeUpdate(Command.java:253) at org.h2.jdbc.JdbcPreparedStatement.execute(JdbcPreparedStatement.java:193) What I don't understand at first glance is the reason for deleting anything from that index. The index is on a single column of the modifed table but it is not used in the update statement that causes the deletion. What the update does is copy the original_genre column into two other columns (genre and lower_genre) of the same table. Background for the use-case, the original_genre column holds the original value while genre and lower_genre hold a possibly modified value. This update statement is for the use-case of resetting the possibly modified values to their original ones. -- 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/groups/opt_out.
