Hi Nikhil,
thanks for reporting this.
However, this is more a feature than a bug in MonetDB --- well, maybe that not that clear / suitable error message might be considered a bug.
For numerical types, MonetDB uses the smallest representable value (per type) as null value, i.e., for a x-bit (signed) integer type, -2^(x-1) is NULL, and "only" -((2^(x-1))-1) - (2^(x-1)-1) is a valid range.
For that standard SQL types, this means the following:
type byte/bit NULL min max
tinyint 1 / 8 -128 -127 127 smallint 2 / 16 -32768 -32767 32767 integer 4 / 32 -2147483648 -2147483647 2147483647 bigint 8 / 64 -9223372036854775808 -9223372036854775807 9223372036854775807
Kind regards, Stefan
On Thu, Mar 22, 2012 at 12:28:54PM -0400, Nikhil Padmanabhan wrote:
Hello,
I have recently started trying out monetdb and have been very impressed by its speed so far.
However, I am hitting a failure trying to read in a large negative number (bitmask) into a bigint field;
sql><test.sql
operation successful
value '-9223372036854775808' from line 1 field 17 not inserted, expecting type bigint
failed to import table
I've attached the sql commands to create the table and a test file to this message.
As far as I can tell, this should be fine for being represented by a 64 bit integer....
I am running this on an OS X 10.6 64-bit system, this is the Dec-2011 SP2 version of the 64 bit binaries dowloaded from www.monetdb.org.
Any help is much appreciated. Thanks in advance, -- Nikhil
Nikhil Padmanabhan nikhil.padmanabhan@yale.edu
This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure
MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users