Never mind. Clearly, I was confusing my models with my forms.
--~--~-~--~~~---~--~~
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 fr
thank you all for your help!
Luis P. Mendes
--~--~-~--~~~---~--~~
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, s
On Sat, Apr 29, 2006 at 08:20:30PM -0500, James Bennett wrote:
> In the tutorial, the field on the Choice model ('poll') is the same as
> the name of the model it's being related to ('poll'), which is why it
> looks that way. Whenever they're different, you want to use the name
> of the field on y
On 4/29/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> This is not what I understood from reading and practicing the tutorial
> 1:
In the tutorial, the field on the Choice model ('poll') is the same as
the name of the model it's being related to ('poll'), which is why it
looks that way. Whene
On 4/28/06, Luis P. Mendes <[EMAIL PROTECTED]> wrote:
> class Servico(meta.Model):
> ~codigo = meta.TextField(maxlength=4)
> ~nome = meta.CharField(maxlength=80)
>
> ~def __repr__(self):
> ~return self.nome
>
> class Cadastro(meta.Model):
> ~serv_cli
This is not what I understood from reading and practicing the tutorial
1:
# The API automatically follows relationships as far as you need.
# Use double underscores to separate relationships.
# This works as many levels deep as you want. There's no limit.
# Find all Choices for any poll whose pub
Luis P. Mendes wrote:
>As _django models_:
>class Servico(meta.Model):
>~codigo = meta.TextField(maxlength=4)
>~nome = meta.CharField(maxlength=80)
>
>~def __repr__(self):
>~return self.nome
>
>class Cadastro(meta.Model):
>~serv_clientes = meta.Fore
7 matches
Mail list logo
