From: Matthew M. <ma...@tu...> - 2003-04-10 13:20:24
|
> Ok, it looks like it doesn't like the "unsigned" tag. >> Postgres does not support the "unsigned" keyword. >> >> Should they need, for some reason, the functionality of an unsigned >> integer, >> you can always create a DOMAIN of int that does not permit values < 0. I believe we can accommodate this, however, we would be losing half the range of an integer field. If an integer is not declared as unsigned, it assumes you will need negative numbers. So half the memory space is reserved for it. Correct me if I am wrong. Should this be something to worry about for primary indecies? Do we need to find out how every DB handles > 0 numbers only? <rant> And what the hell good is a standard if every db does something different? </rant> Matt |