On 4 Gen, 13:41, Gareth McCumskey <gmccums...@gmail.com> wrote: > To be perfectly honest, why bother? What advantage does turning a more > efficient integer based, autoincrement ID column into a more inefficient, > multi-byte character column, even if you could get "autoincrement" working > for characters? Any app that requires a unique ID for the primary key should > work fine integers. Characters just make database slower.
You can find discussions on mysql forum, stating that char key is slower than integer key only if char is longer than 4. IMHO a char primary key is nice when you need a key that is human readable (e.g. for a state/province) I used it myself with any problem. Of course, you need to specify by hand a key value when/if you insert a new row, but that's all. cheers Massimiliano -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
