Dmitrii Aleksandrov

Hi. The issue still reproduces with the setup from my description. Here's an archive just in case: [seaorm-repro-1884.zip](https://github.com/user-attachments/files/15789306/seaorm-repro-1884.zip) Extract it, go to the root and then proceed to steps 3...

Yes, my case is fixed now. Thank you

Do you have any plans regarding reaching version 1.0? You seem to make a new 0.x release every week or so. Many of them don't have any breaking changes, but...

Oh, so that's what has been preventing me from updating to `itertools` 0.13! Thank you.

For the last few months, maintainers pay very little attention to community issues/PRs :( It's weird, given that they still release new versions, blog posts, etc. They're probably focusing on...

FYI: if you have a regular web app and you statically know the schema that you want, you can always just write migrations in raw SQL. This feature is only...

@mpyw, > I find it counterintuitive that calling with `Alias::new("schema_name.enum_name")` results in `"schema_name"."enum_name"`. The identifier should be fully determined at the alias definition stage and should not be modified. I...

@Huliiiiii, > What are your thoughts on this? See above. > Keeping the Iden trait seems to allow for type-specific behavior. Alternatively, we can change the function parameters, or perhaps...

@Huliiiiii, If you mean literally accepting something like `T: IntoIdenOrColumnRef`, that wouldn't work, I think. We can't implement that new trait both for `T: IntoIden` and `T: IntoColumnRef`. There can...

Turns out, `ColumnRef` doesn't make sense either. We need to add a separate type for potentially-qualified names (type names, function names...). See https://github.com/SeaQL/sea-query/pull/922#issuecomment-3131704526. I'll do that