On Monday, May 2, 2011 3:53:47 PM UTC+2, Andreas Henningsson wrote: > On Mon, May 2, 2011 at 3:43 PM, Noel Grandin <[email protected]> wrote: > > Its not a schema change, it will only apply to result sets i.e. if a > > computation in a select would result in an overflow, the result column > > gets automatically promoted to the next larger numeric type. > > that sounds more ok to me.
To me it does NOT. Nearly any computation may overflow, so the result of int+int should be long and long+long should be BigInteger? In general surely not. But then you have a result type depending not only on the type of included variables, but also an their actual values. Would you do this globally or on a per-row bases? The former is impractical, since you'd need to compute the whole ResultSet before returning anything. The latter is weird, weird, weird.... -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
