add json support to SQLA backend #1245
Merged
Conversation
This file contains 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
|
Lets use PostgreSQL 9.4. Otherwise - good to go. |
pawl
force-pushed
the
add_sqla_json_field
branch
from
d815215
to
711b33e
Compare
|
Just changed it to use 9.4 here: 711b33e |
|
@mrjoes I just updated translations. Think we're ready for a release that includes this? |
|
I think so. Do we have anything else pending? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request adds the ability to edit JSON columns to the SQLA backend.
It accomplishes this by moving the GeoAlchemy backend's JSONField into
flask_admin/form/fields.pyto be shared between the two backends. Also, some improvements were made to the JSONField's ability to handle non-ascii characters.Editing:
List View:
Invalid JSON:
