What will be the suggested approach if we where to stick with camel_casing?
Dear ABP Support Team,
I'm seeking clarification on the recommended naming convention strategy when using ABP Framework with PostgreSQL.
While PostgreSQL standards typically use snake_case, we've encountered several challenges when applying this to ABP entities:
1. Inconsistent Casing Enforcement:
* UseSnakeCaseNamingConvention() doesn't fully handle inherited properties (e.g., IsDeleted, CreationTime from FullAuditedAggregateRoot)
* Some generated queries still reference PascalCase names
2. Migration Conflicts:
* Built-in ABP queries expect PascalCase table/column names (SELECT * FROM "AbpPermissions")
* This causes failures when the physical schema uses snake_case
3. Current Workarounds:
* We've tried creating PostgreSQL views as aliases
* Implemented custom IEFCoreNamingConventions
* Used interceptors to rewrite queries
Could you please clarify:
* The officially recommended approach for PostgreSQL naming conventions?
* Whether there are plans to improve snake_case support in future versions?
* Any known workarounds for the FullAuditedAggregateRoot property casing issue?
This would help us align our implementation with ABP best practices.
Best regards,
