Re: Passing parameters to class Meta:

TIL don't override model class constructor if you don't really have to. 

Thanks for all your help guys! Now when I think about it I don't even know why I did it in the first place.

On 17 April 2012 03:12, Javier Guerra Giraldez <javier@guerrag.com> wrote:

On Mon, Apr 16, 2012 at 11:08 AM, Tom Evans <tevans.uk@googlemail.com> wrote:
> Surely you would want what business a payment relates to to be stored
> directly in the database?! At which point it simply becomes an
> additional field in your payment model, and the only problems come
> with automatically populating that field.

my thoughts exactly

--
Javier

--
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.