Since `field_order` will be in Django 1.9 the second clean loop is hardly
needed in my case.
https://github.com/django/django/commit/28986da4ca167ae257abcaf7caea230eca2bcd80
Am 08.04.2015 um 14:20 schrieb Thomas Güttler:
Am 26.03.2015 um 15:12 schrieb Marc Tamlyn:
In particular it is worth
withdraw the proposal. If someone likes to do it: go ahead, and ask
me and other for feedback :-)
Regards,
Thomas Güttler
--
Thomas Güttler
http://thomas-guettler.de/
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django i
ate"')
return
if state != 'wait_until_due_date':
raise ValidationError('If no due date is set, state must be
"wait_until_due_date")
Open questions: I am unsure if this should be used only for validation, or if
it should be possible
to alter values, too.
ew lines of code.
I guess this could be possible. I guess the diff for the docs
could be longer then the diff for the code.
Regards,
Thomas
--
Thomas Güttler
http://thomas-guettler.de/
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contribu
s some magic at the beginning
and end of each transaction.
Can you understand what I wrote?
Will a patch to provide settings.MIDDLEWARES_INSIDE_TRANSACTION be accepted?
Regards,
Thomas Güttler
Am 03.02.2015 um 11:00 schrieb Aymeric Augustin:
Hi Thomas,
Both ways had advantages and drawback
view transaction?
Regards,
Thomas Güttler
--
Thomas Güttler
http://thomas-guettler.de/
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it
d fear: New columns that is outside my current comfort
zone.
I want to use STI the next time I need model inheritance.
Regards,
Thomas
--
Thomas Güttler
http://thomas-guettler.de/
--
You received this message because you are subscribed to the Google Groups "Django
developers&qu
some discussion about this [1]. One reason against it was,
that supporting not-null is not available. But a db constraint which
checks the type and data column could solve this.
What do you think?
Thomas Güttler
[1]
https://code.djangoproject.com/wiki/ModelInheritance#a1
Hello,
I want to improve this method:
django/forms/forms.py: Form.get_changed_data()
I need to have access to the old data, and would like to have a triple list
like this:
(field_name, old_value, new_value)
Code: https://github.com/django/django/blob/master/django/forms/forms.py#L415
My cur
mon tags? Example:
{{{
@register(Tag.COMPATIBILITY)
}}}
Thank you for this check framework. I like it.
Regards,
Thomas Güttler
--
Thomas Guettler, http://www.tbz-pariv.de/
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
T
see it?
Apache can't do it. Or at least it would be complicated.
Thomas
--
Thomas Güttler, http://www.tbz-pariv.de/
Bernsdorfer Str. 210-212, 09126 Chemnitz, Tel.: 0371/5347-917
TBZ-PARIV GmbH Geschäftsführer: Dr. Reiner Wohlgemuth
Sitz der Gesellschaft: Chemnitz R
uot; This
> field is very important for myself, and as evidenced by the level of
> communication and work regarding the ticket it seems to be quite
> important to several others as well.
I used the patch on linux with postgres without problems. I think
it could be commited, too.
--
Thoma
erver. Either in admin or as own application.
Thomas Güttler
--
Thomas Güttler, http://www.tbz-pariv.de/
Bernsdorfer Str. 210-212, 09126 Chemnitz, Tel.: 0371/5347-917
TBZ-PARIV GmbH Geschäftsführer: Dr. Reiner Wohlgemuth
Sitz der Gesellschaft: Chemnitz Registergericht: C
Hi,
it is suprising, that
MyModel.objects.filter()
does not use distinct by default. If you use related tables and OR,
you get the same object returned several times.
Why not enable distinct() by default?
Thomas
--
Thomas Güttler, http://www.tbz-pariv.de/
Bernsdorfer Str. 210-212
14 matches
Mail list logo