oxidecomputer
SeaORM support
Hey this PR sketches out an initial draft of SeaORM support which would allow users to have type safety all the way down to their DB and back.
I thought I'd see what your inclination was for accepting such a PR before working further on it!
If not - happy to maintain a fork for my own purposes.
Thanks. I wouldn't mind supporting this in principle, but the issue is the same as the one I pointed out in https://github.com/diesel-rs/diesel/discussions/3993 -- this is committal in a way that's irreversible, and has negative impacts on the ecosystem. My preference would be for "large" dependencies like SeaORM (or Diesel) to depend on "small" dependencies like newtype-uuid.
At Oxide, within the database layer we've been using our own newtypes that have From and Into conversions (this is partly why I used a type parameter), and it's been okay. Not great but okay. We convert to these types as soon as we retrieve data from the database layer.
