Ivan Krivosheev

> Hey @mohs8421, nice stuffs!! Yes, then we always have a proper index name regardless. > > @ikrivosheev do you still remember the "bug" where MySQL constraint / index name...

@alphavector hello! Any updates?

@billy1624 this is a cool idea! But breaking changes. Well, on the other hand we have been talking about this for a long time and I saw similar issues. If...

@evgeniy-terekhin hello! Sorry with the delay. I think is better split TableOpt into backend specific options, what do you think?

@solidiquis, hello, do you mean that table name should be `users`?

I want to create derive-v2 macros where I merge sea-query-derive and sea-query-attr.

> I guess we can close this? @billy1624 I think, no, we cannot... I will continue work on it.

@billy1624 hello! I think this is not all types... For example: 1. https://docs.rs/sea-query/latest/sea_query/extension/postgres/enum.PgFunction.html 2. https://docs.rs/sea-query/latest/sea_query/extension/postgres/struct.PgFunc.html 3. https://docs.rs/sea-query/latest/sea_query/extension/sqlite/trait.SqliteExpr.html

> Hey @ikrivosheev, I think we shouldn't implement `IntoSimpleExpr` for the types below. > > 1. https://docs.rs/sea-query/latest/sea_query/extension/postgres/enum.PgFunction.html (will not be used directly, instead user should construct it via `PgFunc`) >...

I am also working on `derive-v2` in SeaQuery and I am using darling. I see that the experiment is successful)