Hey Jeremy,
On Fri, 2007-05-04 at 19:44 -0500, Jeremy Dunck wrote:
> Malcolm,
> I noticed that Django's current serialization doesn't deal with unicode
> well.
Too true. :-)
>
> When using MySQLdb with utf8 as the encoding, charfields return
> unicode objects. base.get_string_field break
Malcolm,
I noticed that Django's current serialization doesn't deal with unicode well.
When using MySQLdb with utf8 as the encoding, charfields return
unicode objects. base.get_string_field breaks because it calls str()
on the field, forcing python to use sys.getdefaultencoding().
As a res
Hi Everyone,
I have run into a curious problem while using TextFields (NCLOB
datatype) in the oracle branch.
The problem that I am having is that if I attempt to store a piece of
text greater than 4000 characters in length. The save function will
complete successfully however when I attempt extr
On May 3, 7:18 pm, Brian Rosner <[EMAIL PROTECTED]> wrote:
> I wanted to bring up some discussion here about an empty PATH_INFO
> value. The ticket #3414 also reports this problem.
There is the same problem with CGI.
Please look at: http://code.djangoproject.com/ticket/2407
--~--~-~--
On Sun, 2007-04-29 at 22:22 +0800, Russell Keith-Magee wrote:
> Hi all,
>
> Two suggestions about the newforms API:
These didn't get the overwhelming show of support I was hoping they
might. So my two cents...
>
> 1) Is there room for a 'fields' argument on form_for_instance and
> form_for_mod
