On 4 Jun 2008, at 17:40, Frederick Cheung wrote:
> > On 4 Jun 2008, at 16:58, rob-twf wrote: > >> >> 1. That would be true only for the automatically created primary key >> fields. For all other integer fields the default for unsigned is >> false >> - so nothing changes. > > Does that screw up foreign keys ? mysql is rather nit picky about > the foreign key and the id having the same type (eg you can't have a > foreign key constraint connecting a bigint column on one table to an > int column on another: they both have to be bigints or both ints) > Sigh. it's been a long day. the rest of your mail trickled through. I do share tarmo's concerns (eg when I create a new table with a user_id I have to remember that my users table is old and has a signed primary key) Fred --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
