Allow lowercase naming, for example `ck` instead of `CK`

[warheat1990]

I'm using postgresql and usually everything is in lower case.

[roji]

@warheat1990 are you looking for https://github.com/efcore/EFCore.NamingConventions?

[warheat1990]

@roji what I mean is, by default EFCore.CheckConstraints hardcoded the check constrains as CK_{tableName}_{columnName}_Enum, it would be nice if we have option to make it lower case like ck_{tablename}_{columnname}_enum as postgresql usually use snake_case naming.

[roji]

@warheat1990 are you saying that when using both EFCore.CheckConstraints and EFCore.NamingConventions, you're still seeing uppercase CK instead of the expected lowercase?

[warheat1990]

@roji that's correct, but I'm actually not aware that it's supposed to respect the setting on NamingConvention because I have a quick glance at the code and it seems hardcoded to CK_tablename_columnname_Enum

[roji]

@warheat1990 the point is that the value "hard-coded" by EFCore.CheckConstraints should get processed by the naming convention plugin, and made lower-case at that point. The EFCore.CheckConstraints plugin shouldn't start dealing with naming convention and casing issues on its own, else we start duplicating EFCore.NamingConventions into it.

So this is likely an issue with ordering/interaction of the two conventions coming from the two plugins - I'll try to take a look soon.

[warheat1990]

Here's the code if it helps

builder.Services.AddDbContext<ApplicationContext>(
    options => options
        .UseNpgsql(configuration["DefaultConnection"])
        .UseSnakeCaseNamingConvention()
        .UseAllCheckConstraints()
);

[cremor]

@roji Any news on this? I have the same problem.

[roji]

@cremor no news. I don't expect to have any time to look at it, and in any case this likely requires some infrastructure around EF conventions that isn't there yet, i.e. convention layering (/cc @AndriySvyryd).