For me works like:
[...]
form = ProfileForm(request.POST.copy())
if form.is_valid():
data = form.clean_data
for i in data :
if isinstance(data[i], unicode):
data[i] = data[i].encode(settings.DEFAULT_CHARSET)
[...]
No need to create an old_data.
Ah, data is request.POST, of course, and I create the form like that
myForm(data).
On 7 mar, 23:04, "Baptiste" <[EMAIL PROTECTED]> wrote:
> I had the same problem (ticket 3630).
> I solved that by passing my mySQL fields in UTF8, then by doing :
>
> for i in data :
>
I had the same problem (ticket 3630).
I solved that by passing my mySQL fields in UTF8, then by doing :
for i in data :
data[i] = data[i].decode("latin1","replace")
Then I created a form with these data and used its values to save them
in the DB. If you do
Hello,
We have same problem with character "ä,ö,å". That problem will raise
allways when:
*we try save these character to database
*use characters in field name
*use characters in help_text
--~--~-~--~~~---~--~~
You received this message because you are sub
Hi,
Although seems that exists a patch for this problem, the newforms
continues with the same problem.
I have a field that the user fills with: João Ratão
In the database shows: Jo? Rat
This behavior happens only in the latest trunk, in the old an unicode
exception was raised.
In the Admin interf
