small fixes for use with python 3.4, postgres, and many-to-many relations #165
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Interesting bucket of issues.
FastFixtureTestCase fixes will probably come after REUSE_DB=1 fixes, but if you want to write some tests (#220) and submit individual PRs, it might get fast tracked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
replaced file->open (file is no longer a builtin in python3.4). also postgres is very grumpy about integrity constraint violations (as it should be): it stopped complaining after these fixes. Ah yes... also: table names need to be quoted if e.g. they have the bad taste of using camelcase (which unfortunately one of my apps did).