Re: Design strategy for table with many attributes

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: Design strategy for table with many attributes
Дата
Msg-id CAKFQuwYpai5snt5mEgyXK4m6nR5T6sP-YTYH-GQ0Hs2rXS7uLA@mail.gmail.com
обсуждение исходный текст
Ответ на Design strategy for table with many attributes  (Lok P <loknath.73@gmail.com>)
Ответы Re: Design strategy for table with many attributes
Список pgsql-general
On Thu, Jul 4, 2024 at 12:38 PM Lok P <loknath.73@gmail.com> wrote:

Should we break the single transaction into multiple tables like one main table and other addenda tables with the same primary key to join and fetch the results wherever necessary?


I would say yes.  Find a way to logically group sets of columns together and place those groups into separate tables.  I'd also be looking for cases where multiple columns really should be multiple rows.  This is not uncommon.

David J.


David J.

В списке pgsql-general по дате отправления: