I think that putting warnings about names that might be problematic would be a good addition @Hobo Dev
On Mon, Aug 23, 2010 at 2:27 PM, kevinpfromnm <[email protected]> wrote: > On a side note, might it be worthwhile if not too hard to put in a > check for field and association (model?) names that might be > problematic when doing a hobo_migration and throwing a warning or > error? > > On Aug 21, 10:07 pm, Matt Jones <[email protected]> wrote: >> On Aug 21, 2010, at 7:03 PM, Scorpio wrote: >> >> > I'm working on a products page and its all fine and dandy until I come >> > to attributes and prices (different currencies ). >> > I've been thinking of creating a separate resource Attribute and >> > Price. >> >> Kevin's advice to check out :accessible is right on target; on a >> somewhat unrelated note, note that naming a model 'Attribute' and then >> joining it to Product with a has_many will make Rails get very >> confused, since 'attributes' is a key method from ActiveRecord... >> >> --Matt Jones > > -- > You received this message because you are subscribed to the Google Groups > "Hobo Users" 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/hobousers?hl=en. > > -- - Owen Owen Dall, Chief Systems Architect Barquin International Cell: 410-991-0811 -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
