search

lukesneeringer / django-pgfields

Django field subclasses for some PostgreSQL types.
Other
68 stars 16 forks source link

DJango 1.8 status? #21

Open sknutsonsf opened 9 years ago

sknutsonsf commented 9 years ago

What are the plans for integration/migration to DJango 1.8? It already has some of the capabilities.

lukesneeringer commented 9 years ago

I was kind of thinking about letting support end, and recommending moving to the Django 1.8 native functionality. If Django 1.8 lacks some of the functionality, however, I could absolutely be convinced to continue the project.

sknutsonsf commented 9 years ago

Thanks for clarifying.

Django 1.8 does not have the JSON field type. I'll be trying out the jsonfield module which claims to be 1.8 compatible. I also have to solve the circular foreign key problem with migrations in 1.8.

On Mon, Apr 13, 2015 at 5:55 PM, Luke Sneeringer notifications@github.com wrote:

I was kind of thinking about letting support end, and recommending moving to the Django 1.8 native functionality. If Django 1.8 lacks some of the functionality, however, I could absolutely be convinced to continue the project.

— Reply to this email directly or view it on GitHub https://github.com/lukesneeringer/django-pgfields/issues/21#issuecomment-92549127 .

lukesneeringer commented 9 years ago

If the jsonfield module is not workable, I would be very open to exporting the one that this provides into its own package, geared toward 1.8.