lt;https://engineering.zenefits.com/2015/11/using-old-ideas-to-solve-new-problems/>
.
Do you think that this is a useful feature to have in Django? And if so,
does the proposed patch
<https://github.com/django/django/compare/master...jianli:migration-lock-file>
suffice?
-Jian
On Wednesday, May 17, 2017 at
Hi!
In the course of implementing `natural_key` for many different models, I've
noticed that the implementation is fairly predictable; it tends to use the
fields already marked as unique. To avoid writing a separate implementation
for each model, I've written a patch that implements the relevant l
ny lines of boilerplate.
On Thu, May 8, 2014 at 10:07 AM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
>
> On Wed, May 7, 2014 at 10:20 AM, Jian Li wrote:
>
>> Hi!
>>
>> In the course of implementing `natural_key` for many different models,
>> I'v
/django/compare/master...jianli:migration-lock-file
Hopefully this is useful enough to be merged upstream. Please let me know
what you think, and keep up the amazing work!
-Jian
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to D
