-
-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model Generator failed to generate relation function name in camelcase format when column-name in the database is uppercase #325
Comments
Hmm... how should gii behave if the table name is customer_SSID? |
I think it's better to be generated into getCustomerSsid, then. |
I'd expect it to be getCustomerSSID. |
Hmmm.. if i may ask your opinion, how about CUSTOMER_SSID? |
That's the problem. DB conventions may be different. Either we should introduce different schemas to select or not to change current behavior. |
Agreed.. Hmm.. Is there a way to customize the current behavior? Or maybe any plan to provide a way to customize it? For example: For the sake of clean function naming though. |
Agree. It makes sense the way you've described it. |
If you expect |
This is very similar to #366. But there we have a new form option to enable PSR names. It was not set default for BC. Should it be done here too? I mean, should we have a optional feature or should it be default? I fear to have too much options in gii model generator form. |
What steps will reproduce the problem?
Column name in the database table is in uppercase format, eg. CUSTOMER_COUNTRY_ID
What's expected?
Generate relation function :
public function getCustomerCountry() {...}
What do you get instead?
Relation function will be generated as :
public function getCUSTOMERCOUNTRY() {...}
Additional info
The text was updated successfully, but these errors were encountered: