Re: django 1.4b + mysql + boolean fields

2012-02-24 Thread Ramiro Morales
On Fri, Feb 24, 2012 at 7:53 AM, Tomasz Kloc wrote: > The problem was caused by django.contrib.gis.db.backends.mysql backend. It > has own backend implementation which returns booleans as integers (it was > fixed for 'core' mysql backend in > https://code.djangoproject.com/ticket/13293 ) > > I thi

Re: django 1.4b + mysql + boolean fields

2012-02-24 Thread Aymeric Augustin
I just noticed that #17747 was reopened for this purpose, so there's no need for another ticket. Best regards, -- Aymeric. 2012/2/24 Aymeric Augustin > Please go ahead, create a ticket and set its severity to "release blocker". > > Assuming a proper test was added with the fix for #13293, tha

Re: django 1.4b + mysql + boolean fields

2012-02-24 Thread Carl Meyer
Hello Tomasz, On 02/24/2012 03:00 AM, Tomasz Kloc wrote: > I've changed my database from postgresql to mysql. I have never used > mysql in django projects before, so it was surprising to me when i saw > 0/1 values instead of True/False in boolean fields. It wasn't an issue > until i upgraded djang

Re: django 1.4b + mysql + boolean fields

2012-02-24 Thread Aymeric Augustin
Please go ahead, create a ticket and set its severity to "release blocker". Assuming a proper test was added with the fix for #13293, that test should fail on the geographic version of mysql. Unfortunately we don't have this engine on the CI server at this time. I'll try to add it. Thanks for you

Re: django 1.4b + mysql + boolean fields

2012-02-24 Thread Tomasz Kloc
The problem was caused by django.contrib.gis.db.backends.mysql backend. It has own backend implementation which returns booleans as integers (it was fixed for 'core' mysql backend in https://code.djangoproject.com/ticket/13293 ) I think it's a bug which will afect some users after upgrading to

Re: django 1.4b + mysql + boolean fields

2012-02-24 Thread Tomasz Kloc
Ticket with change described below: https://code.djangoproject.com/ticket/17114 I've also found that since Django 1.2 (https://docs.djangoproject.com/en/dev/releases/1.2/#booleanfield-on-mysql) booleans in mysql backend should be returned as True/False, but i still get ints values. In [7]:

django 1.4b + mysql + boolean fields

2012-02-24 Thread Tomasz Kloc
Hello, I've changed my database from postgresql to mysql. I have never used mysql in django projects before, so it was surprising to me when i saw 0/1 values instead of True/False in boolean fields. It wasn't an issue until i upgraded django from 1.3.1 to 1.4b. After that, all boolean fields