Re: Recomended front ends?
От | Adrian Klaver |
---|---|
Тема | Re: Recomended front ends? |
Дата | |
Msg-id | 3cc9f7ab-2bb8-22c4-5995-63ebcb547240@aklaver.com обсуждение исходный текст |
Ответ на | Re: Recomended front ends? (Rich Shepard <rshepard@appl-ecosys.com>) |
Ответы |
Re: Recomended front ends?
|
Список | 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.klaver@aklaver.com
В списке pgsql-general по дате отправления: