-
Notifications
You must be signed in to change notification settings - Fork 20
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
Any way of keeping the exsisting column names as they are? #36
Comments
Also I am seeing the column name order being re-arranged as in the order changes when output to dataclass |
@avisual I can implement it as a some setting in create_models() method, something like argument 'no_auto_snake_case=True' - to remove auto formatting to snake case that I use in library do you think it should be related only to attributes (properties) of classes or also to class names? |
if you are generating from existing tables keeping the names the same as originals really helps. I know that the purest of coders would say that fails naming conventions. but then we all work in legacy systems or have no control over some data |
@avisual I mean if your table called like 'products' with small case. You want as a result generate |
arg @avisual can you show the sample with columns re-arrange? as input sample - output sample? |
I will close issue as a stale. If it will be still actual - pls open it again |
Sorry had been away on holiday, will try this out today thank you for fixing :) |
We could add this option as a flag for the cli e.g. "--auto-snake" set to false by default |
When using dll with capitals in the name for dataclasses anything with capitals gets renamed such as NHS become n_h_s in the dataclass. is there any way of creating the fieldname as they are in the dll?
GBMSM smallint becomes g_b_m_s_m: int = None
The text was updated successfully, but these errors were encountered: