Open xperiandri opened 1 year ago
I'd have to double check the code, but in general, the provider is opinionated on case for generated fields because postgres in general doesn't handle uppercase gracefully - here's a small example. Though it's against dotnet style guidelines, the provider generates lowercase names to stay consistent with postgres internals which prefer lowercase (it's basically staying away from pain on the SQL side). So in summary, I think this is working as intended, and I wouldn't recommend trying uppercase in column/table names in postgres. Does that make sense?
No, because I use aliases. About column names and other internals I agree. But about aliases I disagree
Having
I get a row with
customerid
andisconfigured
properties instead ofCustomerId
andIsConfigured