Aha, I am starting to see the light.
The weirdness comes from the parser's assumption that strings "2" and
"1073741824" should be typed as int
even though the user has obviously meant them to be of type long or
even BigInteger.
To really fix this issue would be to have only one integer type that
would scale up (to some reasonable upper limit).
For now I think Noel's solution (CALL 2L * 1073741824) is the best.
So thank you Noel for that.
- Rami
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.