Wednesday, May 30, 2012

Re: Django ModelForm user best practices

For example on second method i can change post, board id's via html,
and write to board where i can be banned.
I think we shoudn't override standart methods if we con don't override
them(this about third method)

P.S. sorry for my terrible english.

2012/5/31 Kurtis Mullins <kurtis.mullins@gmail.com>:
>> On second method some experience users can
>> override hidden data
>
> For the second method, you'd just use -- class Meta: fields =
> ('board', 'post', 'name') to prohbit anyone from trying to override
> the 'user', if that's what you're talking about.
>
>> And it's a bad idea to
>> override __init__ and save method in my humble opinion/
>
> What better purpose for the save() method than to save? :) I'm not
> sure why it's a bad idea to override __init__, though. Feel free to
> elaborate. I'm always open for new information!
>
> --
> You received this message because you are subscribed to the Google Groups "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
>

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

No comments:

Post a Comment