I put in *db_table* the table name with the new label prefix and it works, it would be better to automatically identify the new name label created by AppConfig. This seems to be a bug
Em quarta-feira, 10 de dezembro de 2014 17h07min15s UTC-2, Paulo Maciel escreveu: > > I created an app and using AppConfig I changed the label to another name > (abc to my_abc). The migration was successful and the table was created > with the label prefix. But when I access the page, Django emits an error > that is trying to access the table without taking into account that has > changed the name of the label, it is trying to access the table "abc", but > should access "my_abc". > > ProgrammingError > relation "abc" does not exist > > Is it a bug or am I doing something wrong? > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/7df76b38-81c9-498a-ac6a-f07b47acff58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
