auto generate not working for postgres JSONB #411
Comments
Michael Bayer (@zzzeek) wrote: this is of the same class as #85 and the PR we have at zzzeek/alembic#38 would form the basis for the architecture that allows these various Postgresql "nested" types to render directly. |
Michael Bayer (@zzzeek) wrote: |
Changes by Michael Bayer (@zzzeek):
|
Changes by Michael Bayer (@zzzeek):
|
Michael Bayer (@zzzeek) wrote: Apply subtype repr logic to JSON/JSONB Fixed bug where Postgresql JSON/JSONB types rendered on SQLAlchemy Also modifies the ARRAY approach from Change-Id: I66d51301f4bf5b747b5e8da26a83cbff075d71b2 → 9fab143 |
Changes by Michael Bayer (@zzzeek):
|
I cannot get this to work. How are these cases 'closed' when there is no apparent solution??? https://gerrit.sqlalchemy.org/313 -> did not give me any lead, some other sites have these threads that are not trackable, if a bug within Alembic, why is the solution not clear for all's view? |
Hey @joanna350 sorry you're still having trouble. So that I can properly replicate the issue could you provide me with a simple test case, version of postgresql you're running, versions of alembic and sqlalchemy and anything else you think would be helpful. |
I really appreciate this response..and look forward to hearing back in the other thread, or other links that may help. thanks. |
Migrated issue, originally created by Paul van der Linden
When I auto generate a migration for a model with a jsonb field i get the following error:
This is with version alembic
0.8.10
and sqlalchemy1.1.5
, it used to work, and would not add theastext_type=Text()
(in version alembic0.8.9
and sqlalchmey1.0.15
).The text was updated successfully, but these errors were encountered: