On Thu, Jul 14, 2011 at 3:32 PM, Michael Pavling <[email protected]> wrote:
> On 14 July 2011 20:12, joanne ta <[email protected]> wrote: > >> >> Since you took the advice to change the foreign key from "name" to >> "name_id", you need to change the DB field to match. Alter your migration, >> and run it again, or create a new migration to rename the field. >> >>> >>> No, it does not work, :( . it is an error of no column >> table languages has no column named name_id: INSERT INTO "languages" >> "name_english", "created_at", "updated_at", "id", "name_id") VALUES ( >> 'english', '2011-07-14 19:10:54', '2011-07-14 19:10:54', 980190962, >> 64810937) >> >> It is there >> > > > I beg to differ - or at least Rails does. What have you done to check the > field is in the DB? > > I am using the rails dbconsole to check the field in DB > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" 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-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en.
