hmmm, on second thoughts, the whole checking in appserver would add a redundant
overhead (even if slight) cause the db does the check anyway.

there only is a pb when using std number types from backend.
example:

when in gcd we have number(2), we end up using a smallint (i believe it's db
dependent). So where we expect to have a limit of +99/-99, we have +32767/-32767.

The obvious solution would be to avoid that, by always creating a numeric type
(for our example numeric(2,0)). But , as johannes pointed out, a numeric will
always take much more storage size than any int equivalent (5 times more for the
example).

So maybe we could find a compromise, only do the appserver cheking for cases
where we know there could be a pb (ie bigint, integer and smallint).

lekma

warning: i may be completely wrong