On Wed, Jul 28, 2010 at 9:33 PM, Maksymus007 <maksymus...@gmail.com> wrote: > On Wed, Jul 28, 2010 at 3:29 PM, Massimiliano Ravelli > <massimiliano.rave...@gmail.com> wrote: >> On Jul 28, 3:13 pm, knight <alexar...@gmail.com> wrote: >>> What are the minimal changes that I need to make in order to work with >>> 1.2.1? >> >> Did you have a look at >> http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges >> ? > > This link in worth nothing. > The same all the sentences link '1.1 and 1.2 are compatible'. > They are not. > > I have quite big application written in 1.1 - still can't fully run it on 1.2. > As I discovered: forms fields set to be blank=True and null=True when > left blank on 1.1 get null value as expected, on 1.2 the get empty > string - which crashes if database has constraints.
That's a very big claim. Simply upgrading to 1.2 shouldn't require any changes to your source code unless you were relying upon internal APIs or behavior that was buggy in v1.1. We take backwards compatibility very seriously, so if you think you've found a regression, please open a ticket describing the specific problem. If you have already opened a ticket for this problem, then please let me know the ticket number. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
