I can give you many reasons and many details, but I know you will not agree
with my conclusions. I remember what you (or someone from the team) said
about my ideas. I've shared them already and someone told me why you've
decided to do it that way, and why you wouldn't change it. I'm respecting
2016-06-22 14:13 GMT+02:00 Marcin Nowak :
>
> The reason of removing two differenct ways of managing db schema is clear
> for me. I just do not understand removing the tool without providing decent
> replacement for it. For example, CBV generics were replacement for FBV
> generics. There was an in
On Tuesday, January 5, 2016 at 5:29:14 PM UTC+1, Tim Graham wrote:
>
> This came up in a ticket a couple days ago:
> https://code.djangoproject.com/ticket/25995
>
>>
>>
May I ask why this ticket was resolved just by adding some information to
the documentation?
I do not understand why some 3rd
On Wed, Jun 22, 2016, Marcin Nowak wrote:
>On Tuesday, January 5, 2016 at 5:29:14 PM UTC+1, Tim Graham wrote:
>>
>> This came up in a ticket a couple days ago:
>> https://code.djangoproject.com/ticket/25995
>May I ask why this ticket was resolved just by adding some information to
>the documen
>
>
>
> It's not resolved - the ticket is open, and Accepted.
>
>
Thanks. I've seen comment with status set to closed and I didn't notice the
current.
My fault.
Marcin
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django it
Hi again Marcin,
Thanks for this thoughtful clarification. I think I understand your position
much better now. If I understand correctly, there are two issues you find with
migrations:
- They are designed to deal with schema changes, while you'd rather have a
tool for one-time schema generati
