Re: Foreign key auto-created column position in table

> Saying that, why is the order of columns important to you? We don’t > typically worry about the order of columns when working with databases. We have some old software that use "positional" SQL query parameters (like a "INSERT INTO table VALUES(...)" ), so we can't add, remove or move the field

Re: Foreign key auto-created column position in table

No need to worry about columns ordering inside db table -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to thi

RE: Foreign key auto-created column position in table

You can probably just modify the migrations file after it is generated. Just move the statements around. I haven’t tested it myself. Saying that, why is the order of columns important to you? We don’t typically worry about the order of columns when working with databases. From: django-users@g