Integer columns not initialized to handle unsigned 64bit in SQL DB

[rainer]

It's possible that an unsigned 64bit value will be inserted into one of the integer DB columns, but the DB table is initialized to signed bigint, so the inserted value may exceed the maximum allowed value (problem reported by A. Sabitov).

2012-02-13 13:33:03 EST ERROR: bigint out of range
2012-02-13 13:33:03 EST STATEMENT: INSERT INTO log (log_index,log_ref,log_host,log_time,log_sev,
log_msg,path,group_old,group_new,size_old,size_new,
hardlinks_old,hardlinks_new,inode_old,inode_new,imode_old,imode_new,iattr_old,iattr_new,idevice_old,
idevice_new,iowner_old,iowner_new,igroup_old,igroup_new,port,return_code,log_hash) VALUES 
($1,NULL,'dev-windows.[hidden]','2012-02-13 13:32:51','CRIT','POLICY [ReadOnly] -------G--',
'/cygdrive/c/gs','mkgroup','????????',0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,18446744073709551615,0,0,
'D41D8CD98F00B204E9800998ECF8427E')

[rainer]

Believed to be fixed by changeset [392].