Adrian Black

 I think the takeaway is it starts getting painful as soon as you have more than a few thousand migrations, and there will be a practical limit eventually. Worst...

Sure, it's just an extension of the usecase for iteration. For example, if my app stores metadata in sqlite but also stores complex binary data on disk, I might need...

My thought was to have the macro output a `TryInto` impl that maps `migration.version` to the enum discriminant, so no runtime string comparisons. That way the only failure mode for...

It would have to panic on a bad migration version but otherwise sure

Off the top of my head the obvious way to get there (short of `unsafe`) would be to have two sets of embedded migrations for two databases, and then try...