#9422: Make WP transaction safe
-------------------------------+--------------------------------------------
Reporter: Denis-de-Bernardy | Owner: Denis-de-Bernardy
Type: enhancement | Status: new
Priority: normal | Milestone: 2.8
Component: Optimization | Version: 2.8
Severity: major | Keywords: has-patch tested dev-feedback
-------------------------------+--------------------------------------------
Comment(by azaozz):
Do we really need bigint(20) unsigned for all of these fields? Seems
excessive.
`"INT[(M)] [UNSIGNED] [ZEROFILL]
A normal-size integer. The signed range is -2147483648 to 2147483647. The
unsigned range is 0 to 4294967295.
BIGINT[(M)] [UNSIGNED] [ZEROFILL]
A large integer. The signed range is -9223372036854775808 to
9223372036854775807. The unsigned range is 0 to 18446744073709551615"`
Don't think there would be any post_id, user_id, term_id, etc. over 4.2
billion. That would mean a table with 4,200,000,000 rows. Using "normal"
int instead of bigint would make the db size smaller and all indexes
faster. Are there any other reasons why we use bigint everywhere?
--
Ticket URL: <http://core.trac.wordpress.org/ticket/9422#comment:14>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software