Hi!
I've always thought this as well, but I have no strong opinion on it.
Realize that by dropping the () bit from INT you create an
incompatibility with mysqldump (of which we have plenty already).
Cheers,
-Brian
On Jul 23, 2008, at 6:32 AM, Arjen Lentz wrote:
Hi all,
Can we get rid of the (n) in INT(n) nonsense?
I'll admit I've made use of it in combo with ZEROFILL, but really I
was being lazy, other formatting was done in the app, and thus I'd
be happy losing both the (n) and the ZEROFILL completely. The db
should not be involved in output formatting.
Cheers,
Arjen.
--
Arjen Lentz, Founder @ Open Query
Training and Expertise for MySQL in Australia and New Zealand
http://openquery.com.au/training/ (ph. +61-7-3103 0809)
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
