On Thursday, January 15, 2015 at 12:42:31 PM UTC, Yves Senn wrote: > We have descriptive names for indexes because they are shown to the user > in query plans. > This is not the case with foreign keys. When inspecting a database you can > look at the > constraint metadata. I don't see much value in encoding that metadata into > the name. > > In my opinion the drawbacks in the implementation are more sever. We faced > a lot of issues > when automatically renaming indexes. There are still cases where they fall > out of sync > with the actual metadata. Having descriptive names, which no longer > represent the metadata > is way worse in my opinion. > Also constant renaming when renaming tables and columns is not very > practical. The added > issue of the limited size makes this even worse. >
Future versions of PostgreSQL will use FKs within query plans, so constraint names will need to be seen by user. We're looking at probably Sept 2015 for the first version that supports this, which isn't that far away. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
