No, we want to avoid expanding types unnecessarily. That's pretty normal in most languages that value some degree of
performance.
If you want computation on larger types, do this:
CALL CAST(2 AS LONG) * 1073741824
And in the next version, you'll be able to do this:
CALL 2L * 1073741824
On 2013-11-07 12:35, Rami Ojares wrote:
So did I understand this correctly?
You want to limit multiplication to Integer.MAX_INT even though you support the
type BIGINT?
And the reason for this is that PostgrSQL has the same limitation?
--
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.
