Jason Davies wrote:
> Robert Wittams wrote:
>
> [snip]
>
>
>>The other form of subtyping - ( ie is-a relationship) available, is the
>>one-to-one field. This makes a set of fields an extension to another
>>object. The way this is generated in django is to add
>>get_ to each instance of the supe
Robert Wittams wrote:
[snip]
> The other form of subtyping - ( ie is-a relationship) available, is the
> one-to-one field. This makes a set of fields an extension to another
> object. The way this is generated in django is to add
> get_ to each instance of the supertype. A base type
> can have a
Jacob Kaplan-Moss wrote:
However, please note that there are two of us with commit privileges,
and almost 200 open tickets; please be patient!
Thank you for clarification!
I have been thinking about the way subtyping (inheritance) works in django.
Currently (correct me if I am wrong), a model class that inherits from
another model class is treated as a copy of its supertype.
This means it makes a copy of all the fields and methods, possibly
suppressing, and can al
On 9/26/05, Maniac <[EMAIL PROTECTED]> wrote:
> So here are my questions:
> - what is the best way to discuss decisions in tickets and proposing
> patches? (I come from bugzilla.mozilla.org background where patches are
> mainly discussed in bugs' comments)
> - am I doing something wrong? If yes, p
On Sep 26, 2005, at 9:43 AM, Maniac wrote:
I'm a little confused about practices of working with Trac in
Django community and decided to ask here.
[snip]
So here are my questions:
- what is the best way to discuss decisions in tickets and
proposing patches? (I come from bugzilla.mozilla
Hi!
I'm a little confused about practices of working with Trac in Django
community and decided to ask here.
First, some history:
Some time ago I made a patch for ticket 440
(http://code.djangoproject.com/ticket/440) introducing a new config
parameter for default charset. This parameter was
