#django

i'm seeing a weird problem in migrations...

i'll explain

(i'm using ./manage sqlmigrate to check ) the order in wich foreign key are apply, is after the table name is changed...

I think this is better to ilustrate https://dpaste.de/hTd5

did you change a foreign key _and_ a table name?

this is squashed file

and why is there a rename to a table without a prefix?

guys, post_save and pre_save signal. Which one to use when ?

because it's a "main" table in that app. and I want that way

amcorreia: well it's possible you hit a bug, that's not a common use case i suspect

django_unchained: depends on your need

pembo13, hm too bad

amcorreia: you'd need to investigate further to be sure

pembo13: I am confused. It looks like both can be used in any situation.

pembo13, unfortunately, I don't feel confident yet to do this

django_unchained: obvously not, you can use the post_save to modify data after it's been saved to the db

django_unchained: and you may not have a PK during pre_save

s/you can use/you cannot use/