NAMEDATALEN not respected in migrations

[domagojmedo]

Not sure if it's for this or EF core repo. But if your constraint name is longer than NAMEDATALEN - 1 (by default 64) it will just be truncated when creating.
But then if you want to alter anything on that constraint or update it, it will fail because it doesn't exist under the full name, it's under truncated name and EF doesn't track that.

Would it be fine to expose MaxNameLength in options so it's configurable? I know EF can't know what's NAMEDATALEN in your DB but we should be able to specify it so we can avoid EF breaking migrations with longer names

[roji]

This shouldn't be happening - there's specific logic in EF and EFCore.PG for managing maximum identifier lengths.

Can you please submit a runnable repro showing this breaking? Please always do that when opening an issue, as figuring out the problem from a purely textual description (as above) is hard and often impossible.

[domagojmedo]

Sorry, made this as a feature request, not a bug in mind. I'll double check my code first then