"I was recently porting a legacy DB to Django by using the inspectdb command" - is there any reason why you cannot just stop here? Why do you think the "inspectdb" would fail? I would just go on creating the app and if any issues arise, I'd look at the specific model and see if it is because of a DB mismatch. You have no control over the DB, so you'll need to keep adjusting your code as you go on.
On Friday, 7 August 2020 23:20:03 UTC+2, Saahitya E wrote: > > Hi, > > I was recently porting a legacy DB to Django by using the inspectdb > command and then manually comparing the model to the corresponding table > description. I want to confirm that I have not made any mistakes by getting > the corresponding SQL create commands that migrate would have used to > create the model and then comparing it to the original SQL create queries > in my DB. I saw that there was a python3 manage.py sql <app_name> to do > exactly that, but it seems to be depreciated. > > Thanks and regards > Saahitya > > > PS: Using migrations is not possible as other services are using the DB. > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-users/997f639c-5298-4856-a765-026588df61aao%40googlegroups.com.
