Content-Type: multipart/alternative;
 boundary="------------SHWGx61o1lLbR4KcUdtm97YL"
Message-ID: <322e1d7a-7c86-a3e4-4c01-7aaa9b053255@gmail.com>
Date: Thu, 4 Jul 2024 16:35:30 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.10.0
Subject: Re: Design strategy for table with many attributes
To: Lok P <loknath.73@gmail.com>,
 pgsql-general <pgsql-general@lists.postgresql.org>
References: <CAKna9VbQ=o2Yhjo1EitaxzYpWAXe9vw6QtamzCsNNp2-rQOFSA@mail.gmail.com>
Content-Language: en-US
From: Kent Dorfman <kent.dorfman766@gmail.com>
In-Reply-To: <CAKna9VbQ=o2Yhjo1EitaxzYpWAXe9vw6QtamzCsNNp2-rQOFSA@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/322e1d7a-7c86-a3e4-4c01-7aaa9b053255%40gmail.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------SHWGx61o1lLbR4KcUdtm97YL
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: base64

T24gNy80LzI0IDE1OjM3LCBMb2sgUCB3cm90ZToNCj4gT3Igc2F5LCB3aGF0IGlzIHRoZSBt
YXhpbXVtIG51bWJlciBvZiBjb2x1bW5zIHBlciB0YWJsZSB3ZSBzaG91bGQgDQo+IHJlc3Ry
aWN0PyBTaG91bGQgd2UgYnJlYWsgdGhlIHNpbmdsZSB0cmFuc2FjdGlvbiBpbnRvIG11bHRp
cGxlIHRhYmxlcyANCj4gbGlrZSBvbmUgbWFpbiB0YWJsZSBhbmQgb3RoZXIgYWRkZW5kYSB0
YWJsZXMgd2l0aCB0aGUgc2FtZSBwcmltYXJ5IGtleSANCj4gdG8gam9pbiBhbmQgZmV0Y2gg
dGhlIHJlc3VsdHMgd2hlcmV2ZXIgbmVjZXNzYXJ5Pw0KDQo5MDAgY29sdW1ucyBtYWtlcyBt
eSBoZWFkIGh1cnQgYmFkbHkuLi4NCg0KVGhlIG5lb3BoeXRlIHdpbGwgZGVzaWduIGEgdGFi
bGUgd2l0aCBhIHNlcGFyYXRlIGZpZWxkIGZvciBlYWNoIHR5cGUgb2YgDQpwaG9uZSBudW1i
ZXIgdGhhdCBtYXkgYmUgZW5jb3VudGVyZWQuwqAgVGhlIGV4cGVyaWVuY2VkIGRlc2lnbmVy
IHdpbGwgDQptb3ZlIGFsbCBwaG9uZSBudW1iZXJzIHRvIGl0cyBvd24gdGFibGUsIHdoZXJl
IGVhY2ggZW50cnkvcm93IGNvbnRhaW5zIGEgDQpyZWZlcmVuY2UgbGluaywgYSAibnVtYmVy
X3R5cGUiIGZpZWxkLCBhbmQgYSBmaWVsZCB3aXRoIHRoZSBhY3R1YWwgDQpudW1iZXIgaW4g
aXQuLi5UaHJlZSBmaWVsZHMgaW4gYSB0YWJsZSB0aGF0IGlzIG1hbmFnZWFibGUgYW5kIGNh
biBiZSANCnF1ZXJpZWQvbW9kaWZpZWQgd2l0aG91dCBzdHJlc3NpbmcgdGhlIGRhdGFiYXNl
IHNlcnZlci4NCg==
--------------SHWGx61o1lLbR4KcUdtm97YL
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF=
-8">
  </head>
  <body>
    <div class=3D"moz-cite-prefix">On 7/4/24 15:37, Lok P wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:CAKna9VbQ=3Do2Yhjo1EitaxzYpWAXe9vw6QtamzCsNNp2-rQOFSA@mail.gm=
ail.com">
      <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DU=
TF-8">
      <div dir=3D"ltr">Or say, what is the maximum number of columns per
        table we should restrict? 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?<br>
      </div>
    </blockquote>
    <br>
    900 columns makes my head hurt badly...<br>
    <br>
    The neophyte will design a table with a separate field for each type
    of phone number that may be encountered.=C2=A0 The experienced design=
er
    will move all phone numbers to its own table, where each entry/row
    contains a reference link, a "number_type" field, and a field with
    the actual number in it...Three fields in a table that is manageable
    and can be queried/modified without stressing the database server.<br=
>
  </body>
</html>

--------------SHWGx61o1lLbR4KcUdtm97YL--