Skip to content

Feature/pg composite mixed case support #584

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

Merged

Conversation

bamartin125
Copy link
Contributor

Closes #583

@bamartin125
Copy link
Contributor Author

Changes were made to this PR to instead utilize SQLAlchemy's identifier quoting rules/options.

@bamartin125
Copy link
Contributor Author

Well, I had claimed that all tests had passed on my system. The automated test results made me take another look and I obviously found the linting error (newline) I missed in test_composite.py. (now fixed)

I do run into other sqla14 errors on my end as well, but those are not caused by my additions. Another issue will have to solve those errors.

When there are errors in the test results prior to making code changes, it's easy to miss errors that are added. Such is what happened when I added the linting error which I overlooked.

@bamartin125 bamartin125 force-pushed the feature/pg-composite-mixed-case-support branch from 66d26e4 to fee22e1 Compare March 25, 2022 15:47
@bamartin125
Copy link
Contributor Author

I've just squashed my commits and rebased with the latest sqlalchemy-utils master commits.

@kvesteri kvesteri merged commit cb73a37 into kvesteri:master Apr 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CompositeType does not allow mixed case name
2 participants