Dmitrii Aleksandrov

I'm not sure how to force SeaORM to save model fields in a different format. You can apply a workaround at the level of your query. Something like this (not...

> And the problem is, there are other applications which also depend on the same data structure. When now seaORM saves all timestamps in a different format this causes problems...

They seem barely active for the last month or two. I don't know why. You can also try reaching out on their [Discord server](https://discord.com/invite/uCPdDXzbdv).

Well, it's FOSS. It's probably easier to fork and fix the issue than to switch your entire project to a different ORM. I'm in a similar position right now, I...

Ok, if I'm too late for SeaORM 1.0, then I'll go with the backwards-compatible path now. I'll finish with this PR first, then I explore the opportunities to `impl for...

I reverted the breaking impls and updated the PR description. I'll add the documentation in the following days, and then the PR should be ready to merge.

I've added documentation/doctests. The PR should be ready to merge now. The docs are copy-pasted from the original inherent methods of `Expr`/`SimpleExpr`, but adjusted to actually call the trait method....

Technically, this is equivalent to per-cell [set_formula_result](https://docs.rs/rust_xlsxwriter/0.68.0/rust_xlsxwriter/worksheet/struct.Worksheet.html#method.set_formula_result), rather than global per-sheet [set_formula_result_default](https://docs.rs/rust_xlsxwriter/0.68.0/rust_xlsxwriter/worksheet/struct.Worksheet.html#method.set_formula_result_default). But this should be enough for my use case, thank you. I'll close the issue and let someone...

Thank you, this issue is fixed in 1.3.0. But there is another problem with 1.3.0: #207

1.3.0 was yanked and re-released as 2.0.0