Currently second approach with update is implemented.
W dniu niedziela, 19 maja 2013 09:34:18 UTC+2 użytkownik Karol Sikora
napisał:
>
> Hi,
>
> At djangocon sprints I implemented update_or_create method on QuerySet,
> Patch is ready to merge on: https://github.com/django/d
Hi,
At djangocon sprints I implemented update_or_create method on QuerySet,
Patch is ready to merge on: https://github.com/django/django/pull/1132
But after some discussion with folks here and on bugtracker, we need design
decision.
First approach is to following get_or_create approach, passing
I can try to implement approach with pre_syncdb signal tomorrow. I think
that is quite enough solution before deeper diggling into new migrations
framework.
Karol
18 maj 2013 19:03, "Anssi Kääriäinen" napisał(a):
> On 16 touko, 11:20, Danilo Bargen wrote:
> > As a sidenote, there was a discussi
Hi,
We was talked with Russell on djangocon eu about integrating more rich
support for working django as rest api provider, focused on dealing with
one-page web applications.
The motivations that currently without third party modules like
django-rest-framework or tastypie its quite impossible t
Here is my use case.
Model field definition:
blog_url = models.URLField(verbose_name=u'Blog', blank=True,
error_messages={'invalid': u'Adres bloga nie jest prawidłowy'})
To define error messages in form I have to write:
blog_url = forms.CharField(error_messages={'invalid': u'Adres bloga
Hi,
According to my ticket: https://code.djangoproject.com/ticket/18237 and
previous one eg.: https://code.djangoproject.com/ticket/13693 I would to
discuss wider this case.
IMHO redefining field in model form subclass to set custom error messages
is a hardly DRY violation. Currently we have er
