Re: Unintended date to Unicode string conversion

Hi, On Sat, May 23, 2009 at 1:22 PM, Karen Tracey wrote: > On Sat, May 23, 2009 at 1:05 PM, Alex Gaynor wrote: >> >> For what it's worth, neither I, nor anyone else, have ever seen the issue >> on a non-Windows platform.  However, I seem to recall

Re: Unintended date to Unicode string conversion

On Sat, May 23, 2009 at 1:05 PM, Alex Gaynor wrote: > > For what it's worth, neither I, nor anyone else, have ever seen the issue > on a non-Windows platform. However, I seem to recall using a different > SQLite, or python, or something version actually fixes the issue.

Re: Unintended date to Unicode string conversion

On Sat, May 23, 2009 at 11:58 AM, Carlos A. Carnero Delgado < carloscarn...@gmail.com> wrote: > > Hi, > > On Sat, May 23, 2009 at 12:54 PM, Alex Gaynor > wrote: > > There was a bug like this seen when aggregates were first added that no > one > > was ever able to figure

Re: Unintended date to Unicode string conversion

Hi, On Sat, May 23, 2009 at 12:54 PM, Alex Gaynor wrote: > There was a bug like this seen when aggregates were first added that no one > was ever able to figure out.  If you search django-developers you'll see the > discussions of this, it was only ever seen on Windows

Re: Unintended date to Unicode string conversion

On Sat, May 23, 2009 at 11:51 AM, Carlos A. Carnero Delgado < carloscarn...@gmail.com> wrote: > > Hello, > > I'm having a little problem that's making my head hurt. I'm getting an > unintended date to string conversion in my application. > > >>> import django > >>> django.VERSION > (1, 1, 0,

Unintended date to Unicode string conversion

Hello, I'm having a little problem that's making my head hurt. I'm getting an unintended date to string conversion in my application. >>> import django >>> django.VERSION (1, 1, 0, 'beta', 1) >>> import djtest.settings >>> djtest.settings.DATABASE_ENGINE 'sqlite3' Obviously, djtest