On Wed, 2009-02-11 at 22:50 +0900, Russell Keith-Magee wrote:
[...]
> However, in this case, I'm reasonably convinced it is the right thing
> to do. The list of 'ignored' types for force_unicode is essentially
> the list of data types that we use for native data representations. I
> can't think of
On Wed, Feb 11, 2009 at 9:06 AM, Brian Rosner wrote:
>
> Hey all,
>
> I recently came across the issue described in #5903 [1] earlier. There
> are two distinct patches that fix the problem, but at different
> levels. My inclination is to fix this issue at the model field level
> and properly over
On Tue, Feb 10, 2009 at 7:10 PM, Alex Gaynor wrote:
>
>
> On Tue, Feb 10, 2009 at 7:06 PM, Brian Rosner wrote:
>
>>
>> Hey all,
>>
>> I recently came across the issue described in #5903 [1] earlier. There
>> are two distinct patches that fix the problem, but at different
>> levels. My inclinatio
On Tue, Feb 10, 2009 at 7:06 PM, Brian Rosner wrote:
>
> Hey all,
>
> I recently came across the issue described in #5903 [1] earlier. There
> are two distinct patches that fix the problem, but at different
> levels. My inclination is to fix this issue at the model field level
> and properly over
Hey all,
I recently came across the issue described in #5903 [1] earlier. There
are two distinct patches that fix the problem, but at different
levels. My inclination is to fix this issue at the model field level
and properly override get_default. My feeling is that allowing Decimal
objects to pa
