Thanks, Josh. I will be cautious if I ever get to taking this on.
On Tuesday, February 19, 2019 at 9:55:49 PM UTC-5, Josh Smeaton wrote:
>
> To add - there's definitely appetite for this feature, but it's a
> difficult one, and no one has stepped up to do it.
> There are DEP drafts that cover
Lance Ellinghaus wrote:
> Should I consider his statements to be the final statement from the Django
> core developers?
>
of course not, I'm not a core developer.
:-)
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django
To add - there's definitely appetite for this feature, but it's a difficult
one, and no one has stepped up to do it.
There are DEP drafts that cover pieces:
https://github.com/django/deps/blob/master/draft/0191-composite-fields.rst
James,
As a Django user I've had this problem often. My best practice ways to
handle this is as follows:
- If the table is read-only, then create a database-level view that
manufactures a primary key by concatenating the primary key columns
together. Lie to Django and say this
On Tue, Feb 19, 2019 at 4:44 AM 'Lance Ellinghaus' via Django developers
(Contributions to Django itself) wrote:
> Should I consider his statements to be the final statement from the Django
> core developers?
>
> You should take it as someone giving their opinion on the users list.
This is the
I have a number of legacy databases that I need to access from Django and
they do not have a single field primary key. They have composite primary
keys. There is no easy way to add the single field primary key because
other programs create records and Django would not be the application that
