Joseph Kahn

It's done! We've been using it in production basically since Django 2.0 came out. I'll update the docs!

Are you sure it was that one, `PostgresShardGeneratedIDAutoField` uses that default but `PostgresShardForeignKey` doesn't use that from what I can see.

Sorry about that, did a bunch of my other maintainer stuff this past weekend so I'll see what I can do for this one maybe this weekend.

This I have a patch for, I just wanted to iterate in it before documenting it as I only discovered it not that long ago. It's similar to the issue...

The real issue is how do you know if you should consider something missing as "ok" or not. Maybe I can try looking up the Django migration history but then...

Sorry, I haven't been working on this repo much since I haven't used much in the way of Django/Python for work over the past year since switching jobs. My next...

It may be easier to fix this in Django than to try to hack it.

This is the integration I'd like to make use of, but it seems somewhat complicated. I don't know if it matters that it launches a new terminal to do this:...

not necessary, I can just create it with `-d` then attach and all works.

Sorry, didn't notice this. This makes sense, it might be a bracketing issue with the `{`, it isn't detecting a change because whatever value it's setting, it is setting successfully....