New DEP's related to composite primary key and other related improvement of django based on previous works about deps HOT 6 CLOSED

and this one too https://gist.github.com/koniiiik/5450625 with the approach of 2 existing draft dep

from deps.

and this ticket https://code.djangoproject.com/ticket/373

from deps.

https://code.djangoproject.com/ticket/24317 this might need a separate DEP

from deps.

https://code.djangoproject.com/ticket/16508 this needs attention too

from deps.

@auvipy your interest is appreciated, but this is not the correct way to use Issues for DEPs.

Issues should be used to point out a specific problem, or an opportunity for improvement, in an existing DEP, or to comment on one.

Nobody is going to create a DEP based on an issue (at least not like this). Even to start moving, never mind actually to get off the ground, a DEP requires a substantial amount of thought, writing, discussion and other work.

See 6e5ef49 for an example of how much work has to go into what the author calls "a first pre-draft".

from deps.

sorry for being so naive. this should be done in my personal fork auvipy#1

from deps.