Ok, there is an open ticket for this one already:
http://code.djangoproject.com/ticket/6809
-al
On Apr 30, 8:34 pm, Alrex <[EMAIL PROTECTED]> wrote:
> *Correction:
>
> I run a debug on BaseForm and can say that the error does get appended
> to the field named '__all__' ...but it seems that the
On Apr 30, 2008, at 2:33 PM, Ken Arnold wrote:
>
> What would you all think about a Meta attribute for models for
> select_related, analogous to ordering? i.e., default to selecting
> these related fields for any query on this model.
>
> For example, I have a model roughly like:
>
> class Contri
On Apr 25, 2008, at 3:40 PM, Marty Alchin wrote:
> *snip*
> class AuthorProfile(models.Model):
>user = models.OneToOneField(User)
>pen_name = models.CharField(max_length=255)
Now that QSRF has landed, this type of thinking leads me to: who's
working on 121-rewrite? And more important
*Correction:
I run a debug on BaseForm and can say that the error does get appended
to the field named '__all__' ...but it seems that the newforms-admin
form doesn't get the error message.
-al
On Apr 30, 8:22 pm, Alrex <[EMAIL PROTECTED]> wrote:
> As per the doc:
>
> """Note that any errors rai
Rajeev,
How, then, would you suggest handling multiple user groups? To
continue with a similar theme from above, let's say we had two user
groups, Authors and Publishers. When signing up, an Author might need
to input their first name, last name, email, and a password, but a
Publisher would onl
What would you all think about a Meta attribute for models for
select_related, analogous to ordering? i.e., default to selecting
these related fields for any query on this model.
For example, I have a model roughly like:
class Contribution(models.Model):
# content...
creator = models.For
As per the doc:
"""Note that any errors raised by your Form.clean() override will not
be associated with any field in particular. They go into a special
“field” (called __all__), which you can access via the
non_field_errors() method if you need to."""
I can confirm that my ModelForm-based class
On Mon, Apr 28, 2008 at 3:59 AM, peschler <[EMAIL PROTECTED]> wrote:
>
> On 25 Apr., 21:40, "Marty Alchin" <[EMAIL PROTECTED]> wrote:
> >
> > Not to get too much into this discussion, but I tend to be slow to
> > understand design patterns and other paradigms. What then would be the
> > appro
I just started learning about extending Django's User model, so bear
with me as I make sure I understand these things correctly. So we can
subclass the User class doing something like:
class Reader(User):
fields...
class Author(User):
fields...
Does this mean that any new instance of Reade
On Wed, Apr 30, 2008 at 5:22 PM, mrts <[EMAIL PROTECTED]> wrote:
> Looks like enums would be the most natural solution.
> As Python doesn't have enums, class attributes should be used
> (module level globals would clutter the namespace).
>
> Adding to Malcolm's initial proposal:
>
> # django/
Looks like enums would be the most natural solution.
As Python doesn't have enums, class attributes should be used
(module level globals would clutter the namespace).
Adding to Malcolm's initial proposal:
# django/db/models.py
class CreateStrategy:
MUST_CREATE = True
MUST_NOT_CREATE = Fals
On Wed, 30 Apr 2008, Mike Scott wrote:
> The point here is that you were using a development source for your code.
> Understandably people have started using this source more and more due to
> the enhancements and features provided, and its general stability. But it
> is stated everywhere that t
On Tue, Apr 29, 2008 at 1:48 PM, Ed Menendez <[EMAIL PROTECTED]> wrote:
...
> django_session.session_data is made a char(40) instead of a
> varchar(40) most DB engines will make that row a fixed length row
Ed, session_data uses various (non varchar) field types.
I think you must mean session_k
Bikeshedding or not, what about something like
class _default_save_behaviour(object):
pass
...
def save(new_instance=_default_save_behaviour, ...):
if new_instance == _default_save_behaviour:
elif bool(new_instance):
else:
Regards
Niels
On Apr 28, 9:44 pm,
date_hierarchy is broken for me when filtering models with a nullable
date field and at least one instance is None. It raises an
AttributeError " 'NoneType' object has no attribute 'year' ". It seems
the error could be in line 265 of admin's admin_list.py.
Could someone confirm to open a ticket i
15 matches
Mail list logo
