Adriano Caloiaro

@pconstantinou I think we're going to need that reproduction test. I just added [TestFutureJobProcessing](https://github.com/acaloiaro/neoq/blob/main/backends/postgres/postgres_backend_test.go#L779) to cover this case, and it's currently passing. In my manual testing, I tested a few...

I think migrations need a bit more holistic thought at this point. Particularly #77 You raise some important points as well. The motivation behind the auto-migrate concept is that when...

This is good feedback and perspective, so thanks for sharing it. > I think the behavior now is great for users that just care about convenience and are not concerned...

> Oh, the migration files are right there already. So I guess those can be lifted into a different migration system already. Yeah that's right, and it hadn't crossed my...

Hey @gregwebs -- I'm actually thinking of removing migrations in the future, under the assumption that the schema is now stable. Were you able to move forward from our last...

Hi @mgdigital, I'm not at all opposed to refactoring `neoq` such that migrations are optional. At 1.0, I'd like to even remove migrations completely (except for the initial schema bootstrap)....

@mgdigital Neat! Thanks for the heads up.

Hi Philip, thanks for writing in. I've been meaning to overhaul the fingerprint mechanism due to some issues that I've personally had with it, so thanks for providing some additional...

:100:

I think you're right that GC is best left to the library. This request has been sitting in my mental queue for a while. How I'd like to proceed is:...