tically by the form (at least on the admin screen...you'll need to do
> it yourself in your templates as a drop down menu).
>
> At least, this is what I think I would do.
>
> -Tim
>
> On Sat, Feb 27, 2010 at 5:17 AM, django_is
> wrote:
>
> > Yeah I understand tha
primary key*. You don't link to a random field in the model, you always
> link to the primary key.
>
> Does that make sense?
>
> -Tim
>
> On Tue, Feb 23, 2010 at 11:23 AM, django_is
> wrote:
>
> > Thank you for your response. But how would the Orders model
At the moment I am quite
confused about what you mean.
Regards
On 23 Feb., 16:00, Daniel Roseman wrote:
> On Feb 23, 11:56 am, django_is wrote:
>
>
>
> > Hmm ok. Assuming the use case above what would be the correct way to
> > solve this problem? Especially to have the poss
xpected. I just don't know how to
get the payment methods inside the Orders model.
It would be great if you could help me with this.
Thank you very much.
Regards
On 23 Feb., 12:32, Daniel Roseman wrote:
> On Feb 23, 10:21 am, django_is wrote:
>
>
>
> > Hello.
&
Hello.
I got the following use case:
Customer has Payment methods (many to many)
Customer is a Proxy class of User and Customer has a profile which is
connected with AUTH_PROFILE_MODULE to the User/Customer.
Each order has one customer and one payment method (one payment method
from the met
5 matches
Mail list logo