Comment by umairnadeem123

one thing i like about the 'db as library' framing is it forces you to separate a stable api surface from storage internals. but for native image, do you end up baking schema/versioning assumptions into the binary? curious how you handle migrations + backwards compat when the app and 'library db' get deployed independently.