wow, it includes the table name in there? seems redundant. perhaps a constant can be specified for now so people can set where they get warned. the adapter constant is nice, but it'd only really help on the actual migration since the generated migration (and migrations in general) are supposed to be DB agnostic. Unless you're just talking about popping a warning whenever the name exceeds the adapter limit, like 'this migration won't work with oracle/mysql/etc'.
On Oct 14, 3:29 pm, Matt Jones <[email protected]> wrote: > On Oct 14, 2009, at 5:17 PM, kevinpfromnm wrote: > > > > > You could just pop up a warning when name exceeds 30 characters (or > > whatever the lowball is) that the name(s) may not work and leave it up > > to the dev to figure out whether it works in their particular DB. > > The big problem with that is that the Rails default index naming is > pretty chatty; for instance, an index for a polymorphic belongs_to > looks like this: > > index_t_on_f_id_and_f_type > > (t is the table name and f is the association name) That's 23 > characters of boilerplate, plus the table name and the association > name TWICE. It's much less of an issue on DBs with less-gimpy > restrictions, but warning on 30 characters means almost every one of > these will give an error. > > I've opened a thread on rails-core; there really just needs to be a > constant in the DB adapter that specifies the limit. I was stunned > that there *wasn't* such a thing already... > > --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 -~----------~----~----~----~------~----~------~--~---
