On Fri, Feb 22, 2008 at 6:41 PM, Robin Becker <[EMAIL PROTECTED]> wrote:
> Tim van der Leeuw wrote:
> > On Fri, Feb 22, 2008 at 5:17 PM, Robin Becker <[EMAIL PROTECTED]>
> wrote:
> >
> [...]
> >
> > Well -- you escape them in the save() method only when they contain XML
> > charachters like <, > ?
Steve Holden wrote:
> Robin Becker wrote:
>> Tim van der Leeuw wrote:
>>> On Fri, Feb 22, 2008 at 5:17 PM, Robin Becker <[EMAIL PROTECTED]> wrote:
>>>
A colleague has decided to keep his django database string values (which
are xml
fragments) in an xml escaped form to avoid having th
Robin Becker wrote:
> Tim van der Leeuw wrote:
>> On Fri, Feb 22, 2008 at 5:17 PM, Robin Becker <[EMAIL PROTECTED]> wrote:
>>
>>> A colleague has decided to keep his django database string values (which
>>> are xml
>>> fragments) in an xml escaped form to avoid having the problem of escaping
>>> th
Tim van der Leeuw wrote:
> On Fri, Feb 22, 2008 at 5:17 PM, Robin Becker <[EMAIL PROTECTED]> wrote:
>
>> A colleague has decided to keep his django database string values (which
>> are xml
>> fragments) in an xml escaped form to avoid having the problem of escaping
>> them
>> when they are used in
On Fri, Feb 22, 2008 at 5:17 PM, Robin Becker <[EMAIL PROTECTED]> wrote:
> A colleague has decided to keep his django database string values (which
> are xml
> fragments) in an xml escaped form to avoid having the problem of escaping
> them
> when they are used in templates etc etc.
>
> Unfortunat
A colleague has decided to keep his django database string values (which are
xml
fragments) in an xml escaped form to avoid having the problem of escaping them
when they are used in templates etc etc.
Unfortunately he found that the normal admin doesn't escape on the way through
so thought of
