-
Notifications
You must be signed in to change notification settings - Fork 112
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
Autogeneration should respect the specified naming convention #401
Comments
Hi @rushilsrivastava ! (But if anyone else can work on it it would be nice 😉 ) |
Hi @jjgarrett0, did you have some time to work on this? (just to know, no pressure |
@adrien-berchet I have not. Life got in the way, I should have some time this October to take a gander at it though. |
No problem @jjgarrett0, October will be perfect, thanks! |
at
with
we could achieve the results. However we need to handle cases where we're doing Another way could be to extract
but this needs constraint to be present in how would you suggest @adrien-berchet ..? |
Currently, the autogeneration template of indexes is non configurable:
geoalchemy2/geoalchemy2/__init__.py
Lines 47 to 48 in 9d89df1
It would be nice to follow the default conventions established in the metadata if specified, so that it can remain consistent with sqlalchemy.
The text was updated successfully, but these errors were encountered: