Thank you Evgenij, It seems to work.
Meni
On Tue, Aug 6, 2019 at 1:34 AM Evgenij Ryazanov wrote:
> 1.4.196 and older versions have a problem with some constraints. This
> issue was fixed in 1.4.197, but the fix isn't fully compatible with older
> databases. Execution of DDL command in 1.4.197
thanks!
On Tuesday, August 6, 2019 at 6:55:09 PM UTC+5:30, Evgenij Ryazanov wrote:
>
> BTW, take a look on the section “Prepared Statements and IN(...)” in the
> documentation:
> https://h2database.com/html/performance.html#database_performance_tuning
> Please note that ANY(?) is a non-standard
BTW, take a look on the section “Prepared Statements and IN(...)” in the
documentation:
https://h2database.com/html/performance.html#database_performance_tuning
Please note that ANY(?) is a non-standard PostgreSQL-style feature that is
supported since H2 1.4.197. It can be not suitable for
Thank you Evgenij, Life saver.
On Tuesday, August 6, 2019 at 6:43:24 PM UTC+5:30, Evgenij Ryazanov wrote:
>
> Hello.
>
> IN predicate with empty list is not valid according to the SQL Standard.
> However, some databases, including H2, support it.
>
> H2 1.4.193 and later versions don't allow it
Hello.
IN predicate with empty list is not valid according to the SQL Standard.
However, some databases, including H2, support it.
H2 1.4.193 and later versions don't allow it in DB2, MySQL, Oracle, and
PostgreSQL compatibility modes because these databases don't allow it.
When you use a
Hi,
I'm new to H2 db. I'm getting following exception when I try to run java
application using hibernate.
h2 version - 1.4.197
jdk - 8
Please help me.
Caused by: org.h2.jdbc.JdbcSQLException: Syntax error in SQL statement
"SELECT MAX(SCOREBOARD0_.SCORE_BOARD) AS COL_0_0_ FROM SCORE_BOARD
1.4.196 and older versions have a problem with some constraints. This issue
was fixed in 1.4.197, but the fix isn't fully compatible with older
databases. Execution of DDL command in 1.4.197 in the database that was
initially created by some older version may corrupt a database. This issue
was
I have a DB created with older version 1.4.96 and we've upgraded to 1.4.99.
When altering a table to drop a column, it cause table to be renamed, to
something like _COPY_##_## where ## is a number. Once this happens,
it get DB to a corrupted state and it is no longer usable. Is this a known
that is the final work. I'm on it.
BTW thanks.
On Tuesday, August 6, 2019 at 12:29:43 PM UTC+5:30, Noel Grandin wrote:
>
>
> As we said earlier, SQL does not guarantee the sort order of results.
>
> You screwed up, and wrote bad tests, and now you need to fix them.
>
>
>
>
>
--
You received
As we said earlier, SQL does not guarantee the sort order of results.
You screwed up, and wrote bad tests, and now you need to fix them.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails
Hi,
Is this commit affecting my sorting order. Please help me.
https://github.com/h2database/h2database/pull/1707/commits/fa946672364a7b36ecb6c0c678728aab2d0694f5#diff-58e7066f27f34ec51d8ae7f079cca34f
Thanks.
On Monday, August 5, 2019 at 4:22:59 PM UTC+5:30, Pravin Patil wrote:
>
> Sure
11 matches
Mail list logo