In this thread, an Oracle Product Manager (username “Alex Keh”) refused to make Oracle’s EF provider to conform with .NET’s PascalCase coding standard for class names and property names, saying that it is only “cosmetics” without any “functional needs”.
I discussed it with my team. One of the key things we want to know is
why developers are spending so much time changing the case between
Oracle and EF. Is there a compelling functional need to change from
upper case to Pascal case, not just a cosmetic one?On the feature request tool and this thread, people have asked for the
feature, but not offered a reason why Pascal casing is so important
that they would be willing to conduct the manual mapping changes.
For me, the main reason is that I don’t want to see Oracle’s UPPER_CASE name convention mixing in my .NET code, but it seems that this is not enough. How would you justify effort to support PascalCase convention?