-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Lance,
I see that you've already received a number of replies, but I'll give
you my perspective, too.
On Mon, Feb 18, 2019 at 08:26:43AM +, 'Ellinghaus, Lance J' via Django
users wrote:
> NONCONFIDENTIAL // EXTERNAL
> So, basically, Django
Lance,
sincerely, nobody take care about that feature because that's needed just
for legacy db.
The number of applications with on legacy db is less than 0.01% of the
django applications.
There are some workaround for that applications, for example use SQL
Alchemy.
I implemented a CompositeKey
There's general interest in having support for composite keys and composite
foreign key. It's just that nobody has implemented it.
There are proposals among the DEPs that layout ideas how they could be
implemented:
- https://github.com/django/deps/blob/master/draft/0191-composite-fields.rst
-
al Message-
From: django-users@googlegroups.com [mailto:django-users@googlegroups.com] On
Behalf Of Roger Gammans
Sent: Monday, February 18, 2019 11:30 AM
To: django-users@googlegroups.com
Subject: Re: Re: Composite Primary / Foreign Key support
Lance,
I can't speak for the core team, only inform
Lance,
I can't speak for the core team, only inform you based on what I've
seen here and in other projects.
I suspect if there was a significant need across a number of users,
then enough work could be done by those that needed it and as long as
it was
1) fully functional,
2)
NONCONFIDENTIAL // EXTERNAL
So, basically, Django will not be supporting Composite Primary Keys in the
future?
Lance
-Original Message-
From: django-users@googlegroups.com On Behalf
Of Michal Petrucha
Sent: Monday, February 11, 2019 8:34 AM
To: Django users
Subject: [External] Re:
6 matches
Mail list logo
