[wp-hackers] PostgreSQL port status?
computerguru at neosmart.net
Fri Sep 28 14:37:21 GMT 2007
I'm not SURE, but I think one of the guys that work on MySQL told me that using tinyint isn't any different space and performance wise than a int - it's only there as a usage constraint but it takes up the same amount of space on disk....
More importantly, there is no difference between int(x) and int(y) since that only affects how things are *displayed* rather than the actual length that is *stored* (verses string/text fields) and same goes for bigint(x) and bigint(y)...
Here's the manual for the latter statement: http://dev.mysql.com/doc/refman/5.0/en/numeric-types.html
Now as for bigint.....
The biggest number you can store in a bigint is 9223372036854775807 and unsigned is 18446744073709551615
Why would you EVER need such a big number? int()'s biggest is 4294967295 or 4.2 billion..... The biggest auto-increment I can think of is comment indexes, but still, that's HUGE......
> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-
> bounces at lists.automattic.com] On Behalf Of Tom Barta
> Sent: Friday, September 28, 2007 3:59 PM
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] PostgreSQL port status?
> > is there anyone who can explain why there are about 6 integer types
> > the schema?
> > - bigint(10)
> > - bigint(20)
> > - tinyint(1)
> > - int(11)
> > - int(4)
> > - unsigned
> BIGINT may be necessary to support larger sequences/auto-increments,
> and TINYINT(1) IIRC is a boolean flag. Other than that, it's another
> baby step towards MySQL lock-in (^:
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers