forms.URLField and models.URLField not having the same default for verify_exists

verify_exists default to false in forms.URLField and defaults to True in models.URLField. Is there any reasons for that? It can lead to some troubles because it's easy for people to assume that both Fields have the same default. I understand that changing one or the other default now in Django wil

Re: MySQL behavior about Warning/Exception

lain the 2 different behaviors on 2 mostly identical servers? Etienne On Jan 25, 6:34 pm, Dirk Eschler wrote: > Am Dienstag, 25. Januar 2011, 19:48:48 schrieb etienned: > > > > > I would like to understand how Warning/Exception are treated in the > > MySQL backend because

Re: Can I store full dates (mmddyyyy) and year-only dates (yyyy) in the same field?

I had this need some time ago. You can check the answers of my question on stackoverflow for different avenues: http://stackoverflow.com/questions/2971198/how-to-deal-with-partial-dates-2010-00-00-from-mysql-in-django Etienne On Jan 25, 7:22 pm, David wrote: > Malcolm Tredinnick gave a talk at D

MySQL behavior about Warning/Exception

I would like to understand how Warning/Exception are treated in the MySQL backend because I have a weird bug. When I run the test suite of django-reversion on my production server (Ubuntu 10.04) one test fail because MySQL give a warning instead of an exception. If I run the same test on my testin