Re: Recomended front ends?

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Recomended front ends?
Date: 2019-08-08 17:40:59
Message-ID: 3cc9f7ab-2bb8-22c4-5995-63ebcb547240@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 8/8/19 10:34 AM, Rich Shepard wrote:
> On Thu, 8 Aug 2019, Stuart McGraw wrote:
>
>> I would be a little cautious about Django.
>
>> Specifically IIRC it insists that tables have a single-column primary
>> keys.
>
> Stuart,
>
> I looked seriously at Django and did not encounter that limitation.
> However,
> I did learn that I'm not a web application developer nor do I want to be.
> The applications I develop, primarily for my own business needs. use
> SQLAlchemy and that allows multi-column primary keys. That's a necessity
> for
> many-to-many tables (or SA classes).
>
> I suspect that Django also allows multi-column primary keys but the syntax
> might not be obvious.

Unfortunately it does not:
https://code.djangoproject.com/wiki/MultipleColumnPrimaryKeys

Given that the issue:

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

is 14 years old does not inspire confidence that it will change anytime
soon.

>
> Regards,
>
> Rich
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rich Shepard 2019-08-08 17:47:47 Re: Recomended front ends?
Previous Message Rich Shepard 2019-08-08 17:34:51 Re: Recomended front ends?