Re: Test projects needed for removal of Field.get_db_prep_lookup()/get_prep_lookup()

Just bumped up against this in Django-MySQL, fixing in django-mysql/pull/292 . In most cases it's easy to work around, but this usecase is not the most fun - wrapping values for the default lookups on the JSONField: https://github.com/adamch

django-mssql present and future

There are two parts to this email. First relates to the current state of django-mssql. A version of the backend that supports Django 1.8 will be released in the next few weeks. I apologize for the delay, but my ability to focus on the project was basically non-existent for nearly a year due to pers

Re: Better form fields for django.contrib.postgres.fields

A couple suggestions: It'd be better to propose each enhancement separately (and on this mailing list, rather than in Trac) rather than combining them into one ticket. It's not obvious to me that all the proposed features which mainly involve forms should be declared at the model level. I guess

Re: Better form fields for django.contrib.postgres.fields

Hi, The first step is the ticket need to be accepted and then push the change as pull request on master branch. Thanks On Monday, May 23, 2016 at 6:56:43 PM UTC+6, Paul Martin wrote: > > Hi, > > This is my first time contributing to Django. It's a lot of different > features in one to improve

Better form fields for django.contrib.postgres.fields

Hi, This is my first time contributing to Django. It's a lot of different features in one to improve how form fields are produced for ArrayField, HStoreField and JSON FIeld. I opened a ticket here with more details and a screenshot of the admin for a sample model. https://code.djangoproject.c