[h2] Re: Error during database recover

Hi, I see it has been fixed Nov 26, 2023 https://github.com/h2database/h2database/commit/51427805f05782adda33f3c1ccc464544e0d2273 by throwing a MVStoreException in Chunk.readChunkHeader() Still have this question: I was also wondering where the mv.txt dump file is used for. I only need

[h2] Re: Error reading existing databases with H2 trunk

Hi Andrei, Yes, that is what I was expecting. Makes perfect sense of course. SQL dump/restore broke when going from 1.4.x to 2.x.x and we found no way to work around that. We came up with our own dump/restore format that only reuses the DDL part of the old database which seemed to be

[h2] Re: Error reading existing databases with H2 trunk

Hi Silvio, SQL dump / restore is the only supported way to transition from one version to the other. We are making our best trying to preserve compatibility with older db files, but again, it's on a "best effort" basis. Forward compatibility is totaly out of question. And that's I've been

[h2] Re: Error converting value

Thanks Evgenij, That is clear enough. Intuitively I would have expected a conversion to the column type because apart from only having one conversion that would have been the only way to use an index on the column. But that is just me. Lacking standard behavior rejecting the comparison sounds

[h2] Re: Error converting value

Hello! In the SQL Standard all character strings with universal character set (H2 doesn't have any other character sets) are comparable with each other and all numbers are comparable with each other. Comparison operations between different groups of data types aren't described, so there is no

[h2] Re: Error on NaN literal in SQL statement

Hello Evgenij, Thanks for the swift response. That is just the information I was looking for. Thank you very much. Kind regards, Silvio On Thursday, 26 January 2023 at 15:25:14 UTC+1 Evgenij Ryazanov wrote: > Hello! > > NaN is not a literal, it's just an identifier. > > In this case you can

[h2] Re: Error on NaN literal in SQL statement

Hello! NaN is not a literal, it's just an identifier. In this case you can pass it as a character string literal: INSERT INTO "TABLE"(ID, DOUBLE_COLUMN) VALUES (10, 'NaN'); In more complex cases where data type cannot be determined automatically a cast is needed: CAST('NaN' AS DOUBLE

[h2] Re: ERROR SqlExceptionHelper: Unknown data type: "unsigned"

Hello. CAST in MySQL and its forks is not compliant with cast specification from the SQL Standard and is not compatible with other database systems. H2 cannot emulate this deviation. You can replace it with something like case when sequence >= 0 then sequence else sequence +

[h2] Re: Error 50000-210: org.h2.jdbc.JdbcSQLNonTransientException

Thank you both for the responses. Upgrading to 2.1.212 did resolve the issue. On Saturday, April 9, 2022 at 6:55:42 PM UTC-5 andrei...@gmail.com wrote: > I wonder, if you hit this bug > > It was fixed in a newly released 2.1.212 > > > > On

[h2] Re: Error 50000-210: org.h2.jdbc.JdbcSQLNonTransientException

I wonder, if you hit this bug It was fixed in a newly released 2.1.212 On Thursday, April 7, 2022 at 7:01:21 PM UTC-4 Jake Dunn wrote: > I've been trying to resolve this issue when running an integration test > against an in-memory H2

[h2] Re: error version 2.0.204

Hello. H2 2.0 allows up to 1048576 characters for this data type: https://h2database.com/html/datatypes.html#character_varying_type For larger values you need to use CLOB: https://h2database.com/html/datatypes.html#character_large_object_type Please note that PreparedStatement.setString() and

[h2] Re: Error Building H2 Console Servlet

Hello. Unfortunately, if you want to compile H2 1.4.200 or older versions from their sources you have to patch them by yourself or you can pre-download their dependencies. Current H2 can be compiled without any changes or additional actions. H2 1.4.200 should normally be compiled with

[h2] Re: Error only if there is some value

Hello. There is an optional feature T301, “Functional dependencies” in the SQL Standard. H2 and some other DBMS support this feature. Only DBMS without its support may throw an exception immediately. In DBMS with its support select expressions and where cause may reference non-aggregated

[h2] Re: error

Hello. It's just a bad error message, it shouldn't mention the IFEXISTS parameter. The next version will throw a better message. Recent versions of H2 don't allow remote creation of databases any more due to security reasons. You need to create the new empty database in some other way.

Re: [h2] Re: error connecting to h2 database

Thank you On Wed, Feb 13, 2019 at 2:10 AM Evgenij Ryazanov wrote: > Hello. > > It looks like you updated version of H2 database to 1.4.197 from some > older version, executed a DDL command after it, and closed the database. > There is an incompatible change in this version. > > The safe way to

[h2] Re: error connecting to h2 database

Hello. It looks like you updated version of H2 database to 1.4.197 from some older version, executed a DDL command after it, and closed the database. There is an incompatible change in this version. The safe way to update your database to 1.4.197 format is to export it to SQL with SCRIPT TO

Re: [h2] Re: Error: Unpexpected code path

Thank you for this. that will solve my problem with the next release. I will just have to skip 197. -- 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

Re: [h2] Re: Error: Unpexpected code path

Hey Silvio, We noticed this with our own software stack and I managed to track down the cause. It's currently fixed in the master branch but isn't in a released version of H2 yet. Jesse On Wed, Aug 22, 2018 at 8:25 AM Silvio wrote: > I would like to add that most of the applications is

[h2] Re: Error: Unpexpected code path

I would like to add that most of the applications is working fine and the databases can be accessed for the most part. Only specific application functions (in this case removing records from a couple of tables) is affected. -- You received this message because you are subscribed to the Google

[h2] Re: Error: Unpexpected code path

Thanks for the response. Our system supports exporting (and subsequently importing) a "subsystem" including its database in either raw or SQL formats. So I did this and that does resolve the issue. But I must add that importing a subsystem that was exported in SQL format automatically results

[h2] Re: Error: Unpexpected code path

I added a stack trace from a similar failure. This is in a PageStore database. Relevant part of stack trace: org.h2.jdbc.JdbcSQLException: General error: "java.lang.RuntimeException: Unexpected code path" [5-197] at org.h2.message.DbException.getJdbcSQLException(DbException.java:357) at

[h2] Re: Error: Unpexpected code path

For information: The only one reliable way to upgrade from 1.4.196 to a more recent version is to run SCRIPT TO 'filename.sql' in this version, then create a new empty database in a new version and finally run RUNSCRIPT FROM 'filename.sql'. Script tool from 1.4.196 and RunScript from 1.4.197

[h2] Re: error on connecting to database

Hello. You can try to specify a database listener in database URL parameter: ;DATABASE_EVENT_LISTENER='sample.MyListener' Listener should be in your classpath and implement org.h2.api.DatabaseEventListener. http://www.h2database.com/javadoc/org/h2/api/DatabaseEventListener.html -- You received

Re: [h2] Re: Error creating meta-records on application start-up

Thanks! On Thu, Apr 12, 2018, 04:02 Evgenij Ryazanov wrote: > Hello. > > H2 has own script tool > http://www.h2database.com/html/tutorial.html#upgrade_backup_restore > and also SQL command for export. > http://www.h2database.com/html/grammar.html#script > SCRIPT NODATA TO

[h2] Re: Error creating meta-records on application start-up

Hello. H2 has own script tool http://www.h2database.com/html/tutorial.html#upgrade_backup_restore and also SQL command for export. http://www.h2database.com/html/grammar.html#script SCRIPT NODATA TO 'filename.sql' Your SQL script from IntelliJ is not valid. There is no data type TIMESTAMP WITH

Re: [h2] Re: Error 50200-192 if delete from table after upgrading from 1.3.176 to 1.4.192

Short of debugging it itself, your best bet is to do dump before the upgrade, and a restore to a fresh db after. -- 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

Re: [h2] Re: Error 50200-192 if delete from table after upgrading from 1.3.176 to 1.4.192

What's the status of this? We ran into the same issue when upgrading from 1.3.176 to 1.4.195 for our Android app. You can see more details here : http://crashes.to/s/97b4cacc8ab. Anything we can do to assist? Regards Carl On Wednesday, October 26, 2016 at 4:39:36 PM UTC+2, Stuart Goldberg

Re: [h2] Re: Error 50200-192 if delete from table after upgrading from 1.3.176 to 1.4.192

Please take a look at my post a number of months ago entitled "Timeout trying to lock table". This is the same problem! There is a bug somewhere. This issue continues to plague us intermittently. On Monday, September 12, 2016 at 2:38:13 AM UTC-4, Dave Anonymous wrote: > > > Sorry, but I'm not

Re: [h2] Re: Error while executing query "Subquery is not a single column query; SQL statement:"

we don't support multiple-column-IN queries, you'll need to rewrite it as a JOIN​ -- 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] Re: Error while executing query "Subquery is not a single column query; SQL statement:"

Have you tried concatenating the two columns into one column? I don't know if that would work, just an idea. PS: I think you'd have more success finding a solution if you post this on stackoverflow.com On Wednesday, 5 October 2016 09:14:06 UTC+2, Ramesh Elkaturi wrote: > > Hi all, > > >

Re: [h2] Re: Error 50200-192 if delete from table after upgrading from 1.3.176 to 1.4.192

> Sorry, but I'm not going to find time to track this down. > At a guess I would say it might have something to do with the Timestamp > column > isnt it possible to debug this with my attached sql script to reproduce the issue? it is very important for us to know which tables could be

Re: [h2] Re: Error 50200-192 if delete from table after upgrading from 1.3.176 to 1.4.192

Sorry, but I'm not going to find time to track this down. At a guess I would say it might have something to do with the Timestamp column -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails

[h2] Re: Error 50200-192 if delete from table after upgrading from 1.3.176 to 1.4.192

@Noel could you reproduce the issue? -- 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

Re: [h2] Re: Error working with table if they have non standart chars in name (1.4.91)

Do you mean that in Oracle your original scenario will work? create table "$Test"(...); insert into "$test" ... I really doubt. In Oracle docs it is clearly stated that "Nonquoted identifiers are not case sensitive. Oracle interprets them as uppercase. Quoted identifiers are case sensitive."

[h2] Re: Error working with table if they have non standart chars in name (1.4.91)

I did verification of the behavior in the "style" of Oracle: CREATE TABLE test (id int NOT NULL); -- ok CREATE TABLE "TEST" (id int NOT NULL); -- Error: Table "TEST" already exists; SQL statement: CREATE TABLE "TEST" (id int NOT NULL) [42101-191] It seems to me that such an ambiguous

[h2] Re: Error working with table if they have non standart chars in name (1.4.91)

How should I specify object names in the query, where there are such characters if double quotes require guidance caseful object name? I know in other DBMS quotes do not affect the case sensitive. -- You received this message because you are subscribed to the Google Groups "H2 Database"

Re: [h2] Re: Error selecting a constant

Hmmm, the root of the problem is that we need to know the types of columns when creating a query plan. I'm not aware of any standard SQL way of doing that. If it's H2 specific, then using the CAST operator around the constant should give us enough information. On 2016/02/12 11:55 PM, 'David

[h2] Re: Error selecting a constant

I did some more experiments: select 'Hello' as X => ok select ? as X => ok select X as Y from (select 'Hello' as X) => ok select X as Y from (select ? as X) => error "Unknown datatype X" Really surprising, and makes me curious about how a difference could be implemented there in the first

Re: [h2] Re: Error using merge on a table that has a column with a default value.

Hi, Why is this not accepted? I don't know. Sometimes messages are marked as spam by the Google Group system. Usually I get a notification if that happens and can approve the email. But in this case, I didn't get a notification. Not sure why, maybe it's related to using Nabble.com?

[h2] Re: Error using merge on a table that has a column with a default value.

Why is this not accepted? -- View this message in context: http://h2-database.66688.n3.nabble.com/Error-using-merge-on-a-table-that-has-a-column-with-a-default-value-tp4029698p4029702.html Sent from the H2 Database mailing list archive at Nabble.com. -- You received this message because you

[h2] Re: error [90112-178] when executing delete statements

I removed the FK contraint and hence the index CONSTRAINT_2_INDEX_2 - and that seems to have fixed the issue. It would be good to know why that error occured in the first place tho. On Wednesday, 18 June 2014 10:42:12 UTC+1, Mahen Perera wrote: Hi, I am using h2 version 1.4.178, and get

[h2] Re: Error when opening the database a second time

I solved my problem by downgrading to h2-1.3.172.jar 1.3.176 or 1.3.178 wouldn't open my database Unique index or primary key violation 1.3.172 opens it just fine. Maybe try the same Le mercredi 21 mai 2014 19:47:54 UTC+2, Ospeleo a écrit : hi, it is the same error message I have reported

[h2] Re: Error when opening the database a second time

hi, it is the same error message I have reported on this subject, posted today: https://groups.google.com/d/msg/h2-database/iPAECUAML4Y/70PkSslWInQJ I access my database via my application/ Works great. I want to manipulate the table. The same error than yours. Le mercredi 21 mai 2014

Re: [h2] Re: Error 90052, Subquery is not a single column query

Hi, No, I'm sorry, I don't have a solution for this. Patches are welcome! According to my test, MySQL, PostgreSQL, and HSQLDB support this. Apache Derby and H2 do not. I think the typical solution would be to use a join. Regards, Thomas On Fri, Sep 20, 2013 at 6:38 PM, Markus Waltl

Re: [h2] Re: Error 90052, Subquery is not a single column query

Hello The odd background-info from me ;-) This is called an IN predicate on row value expressions. I have brought this up before on this user group, as I think that true row value expression support would be a good feature addition for H2:

Re: [h2] Re: Error 90052, Subquery is not a single column query

... I'm sorry, I was missing the fact that you were using Hibernate. I guess Hibernate will have to be fixed according to what I mentioned below... Am Mittwoch, 25. September 2013 07:29:36 UTC+2 schrieb Lukas Eder: Hello The odd background-info from me ;-) This is called an IN predicate on

Re: [h2] Re: Error 90052, Subquery is not a single column query

Hi, thank you for your elaboration on the issue. I already posted in the Hibernate forum about this issue but it seems they are not reacting act the moment (did not receive any comment on it). I saw the same issue happening with the H2Dialect on commit drop which was indicated by others but

[h2] Re: Error 90052, Subquery is not a single column query

Hi, is there already a solution for this planned? As the current version still does not support this kind of queries. I am using H2 with Hibernate and have the issue that Hibernate generates a query with multiple columns in the subquery which I cannot modify. Do you have a solution for this,