On Wed, Jan 26, 2011 at 4:57 PM, etienned wrote:
> Thanks for your answer.
>
> I have compared the .cnf on both of my servers and they are identical?
>
> Then, in my settings.py file, I set my database options to
> 'sql_mode' : 'TRADITIONAL' and now I don't have the error anymore. So
> that fix my
Thanks for your answer.
I have compared the .cnf on both of my servers and they are identical?
Then, in my settings.py file, I set my database options to
'sql_mode' : 'TRADITIONAL' and now I don't have the error anymore. So
that fix my problem.
But that doesn't explain the 2 different behaviors
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 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 w
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
4 matches
Mail list logo
