Hi Ryan, I agree, I have had applications use uint types to avoid using a larger data type. I have actually had to patch an application developed for MySQL uint8 to signed int8 on PostgreSQL. In that case, the only operations that were performed where assignment and lookup. If we need to use the numeric type for calculations, that would be okay as long as the data is actually stored as 8-bytes, not numeric. It would certainly increase the ease of moving an application from MySQL to PostgreSQL.
Cheers, Ken On Fri, Jul 25, 2008 at 08:50:02PM -0700, Ryan Bradetich wrote: > Hello Dann, > > On Fri, Jul 25, 2008 at 1:06 PM, Dann Corbit <[EMAIL PROTECTED]> wrote: > > > At the cost of one bit of storage, you have compatible types using > > Thanks for your review and feedback! Unfortunately, I do need the full range > of the unsigned types for the project I am looking at. The reason I started > working on these types is because it seemed wasteful to use the next size > larger signed integer for the storage type of the unsigned integer. > > Thanks for the suggestion! > > - Ryan > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
