Re: Automatically creating fields

2010-09-21 Thread tsmets
I think, one of the question is also ... What are these fields for ... ? If they are derived values like : is_firstname_filled or is_age_above_18 you should then just implement a method ... but bottom line, it looks much simpler / efficienter / safer to implement it (as an attribute or a method) in

Re: Automatically creating fields

2010-09-20 Thread pixelcowboy
I get what you are saying, you are right in that it might make more sense to do it for every field that needs it. Thanks. On Sep 20, 11:22 am, Shawn Milochik wrote: > There are always ways. You could subclass models.Model and add the behavior, > if you read enough to understand how Django's mod

Re: Automatically creating fields

2010-09-20 Thread Shawn Milochik
There are always ways. You could subclass models.Model and add the behavior, if you read enough to understand how Django's models work. However, since you're only going create a model once (except migrations later), is it really going to save that much work? If you want to do it a quick & dirty

Automatically creating fields

2010-09-20 Thread pixelcowboy
Hi, for every field in a model that I have created, I want to create a releated boolean field. Is there any way to do this automatically? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegro