Hi all, I've a working PR that implements this but in a much inferior way
https://github.com/django/django/pull/5904
I'm very interested in this and would love to contribute. Has anyone
started work on this? If not, I'd like to pick it up.
--
Owais
On Tuesday, August 4, 2015 at 12:05:33 AM
Shai and Ayeric, thank you so much for the feedback. The PR did indeed
snowball into a much bigger one that I had initially planned. I agree with
all points except,
> - controlling this behavior in the query rather than in the field
definition — this avoids the awkward “ignore what the field
k of response here.
>
> On Wednesday, January 6, 2016 at 10:04:51 AM UTC-5, Owais Lone wrote:
>>
>> Hi, I would really appreciate if someone could review the API design (and
>> implementation) for a PR I created. The PR implements support for fields
>> that are assigne
Hi, I would really appreciate if someone could review the API design (and
implementation) for a PR I created. The PR implements support for fields that
are assigned a value by the database (using a default value or trigger) instead
of Django. It also adds support for PostgreSQL’s RETURNING and
at: https://github.com/django/django/pull/5904
I would really appreciate if someone could take a look at it and guide me
in the right direction.
Thanks
- Owais Lone
loneow...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contribu
