Accessing model fields by name

Hi, I am using setattr(self, fieldname, value) to set a value on a field for which i do not know anything but the name. Is that common django idiom, or are there better ways to do this? eelco --~--~-~--~~~---~--~~ You received this message because you are subscr

Re: Accessing model fields by name

On Jun 4, 1:30 am, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > > I am using setattr(self, fieldname, value) to set a value on a field > > for which i do not know anything but the name. Is that common django > > idiom, or are there better ways to do this? > This isn't a Django-specific f

MySQL and ë, û, á, etc.

Hi, I have a new problem wit mysql and the character set, especially wit the use of the trema (umlaut, diaeresis, whatever) and other special characters. The strange thing is, it is only since a week or so, because i have evidence it worked before. The problem is there with all models. So what c

Re: MySQL and ë, û, á, etc.

On Jun 6, 12:21 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > What version of django are you using? Django version 0.97-pre-SVN-7574 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To

Re: MySQL and ë, û, á, etc.

I have found out that the problem seems to happen on TextFields only. I do not have a problem with CharFields. eelco --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send

Re: MySQL and ë, û, á, etc.

On Jun 7, 1:05 am, eelcoh <[EMAIL PROTECTED]> wrote: > I have found out that the problem seems to happen on TextFields only. > I do not have a problem with CharFields. > > eelco I fixed it by adding the following to the TextField class in /django/ db/models/db/fields/__i