Sadly sqlx seems to have gone semi-proprietary with their MSQL driver. Personally never understood the appeal of mssql when there’s Postgres and SQLite, but hey, it does work.
I’ve started using welds as my new ORM of choice as SeaORM and Diesel is just not a friendly experience, and supports Mssql OOB. So it’s nice there’s still options for it.
Half joking. Lifetimes can be hard but once you understand the concept it’s quite easy.
The second joke is about you never learn Rust. You’re always on the learning rollercoaster. Always one step away but each time it makes you rethink the whole language.
Don’t get me wrong, I’m a rust main. But does issues does exist
Rewrite it in rust. Now get a lifetime of problems
What? No! I leave at 6pm. (But start at 2)
I get 100m up front, right?
Right?
Probably a joke
I would do that… If CI wouldn’t be set to -D warnings
Who even does that? Oh wait, it was me.
Joke aside, it does help to keep the code clean, even more for open source projects where multiple separate people may all have their own codding style, and it helps make it easier to organise.
But I do agree that it can be really, really annoying.
proud Rust developer
Joke aside, everytime people gush over AI, I always have to remind them that AI is just a puppy that learnt how to maximise treats, and not actually understand shit. And this is a perfectly good example.
I work on a proprietary language that translates everything to uppercase before compiling. So having a specific case is useless. The standard functions all have wacky cases. Some from the same module may use CamelCase, while it’s brother use snake_case.
… I just use Rust’s style. Simple, easy.
At least there’s tree shaking. Not everything is getting in the final build
No idea for Tiberius, but for SQLite I’m stuck with converting to timestamp and back. Ugly but works
P.S. add a getter to your data struct and you can be “seamless”