public inbox for [email protected]  

help / color / mirror / Atom feed

From: Wetmore, Matthew  (CTR) <[email protected]>
To: Sanjay Minni <[email protected]>
To: JORGE MALDONADO <[email protected]>
Cc: [email protected] <[email protected]>
Subject: One parent record with 3 possible child records
Date: Thu, 2 May 2024 14:37:09 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAMpxBokoRxVgPVXTKeLV3jb+vA-wsDnwVsH_V_hQw=gATkCvoQ@mail.gmail.com>
References: <CAAY=A79usb2Lbr9nUyzxyRNWLQNc-w3oTBbtUGyC2a4E-qaX3A@mail.gmail.com>
	<CAMpxBokoRxVgPVXTKeLV3jb+vA-wsDnwVsH_V_hQw=gATkCvoQ@mail.gmail.com>

Wouldn’t page size performance be decreased with a very wide table?  Unless the columns are tight.  If you are on a VM subsystem, that page bloat will be over the network from the memory controller.

From: Sanjay Minni <[email protected]>
Sent: Thursday, May 2, 2024 6:34 AM
To: JORGE MALDONADO <[email protected]>
Cc: [email protected]
Subject: [EXTERNAL] Re: One parent record with 3 possible child records

maybe unorthodox but if its certain to be 1:1 then why not flatten it to a single table with all the possible columns (tblMain+tblOne+tblTwo+tblThree). You can keep a flag to indicate the type. there may be a gain in simplicity without losing anything.

Sanjay

On Thu, May 2, 2024 at 4:39 AM JORGE MALDONADO <[email protected]<mailto:[email protected]>> wrote:
Hi,

I have one table that can have relations to only 1 of 3 possible tables. For example: tblMain, tblOne, tblTwo and tblThree.

I will always have 1 record in tblMain but each record in this table will be related to one record in tblOne OR one record in tblTwo OR one record in tblThree.

The relation between tblMain and tblOne is 1:1.
The relation between tblMain and tblTwo is 1:1.
The relation between tblMain and tblThree is 1:1.

Is it better to set tblMain as parent or child?

This can be seen as if tblOne, tblTwo and tblThree extend tblMain depending on a specific criteria.

Let's say that tableMain has a string field called "type" with the following possible values: "residential", "industrial" and "energy".

I will always insert a record in tblMain but:
* If type is "residential" then a record in tblOne is created and it is associated to tblMain,
* If type is "industrial" a record in tblTwo is created and it is associated to tblMain
* If type is "energy" a record in tblThree is created and it is associated to tblMain.

I am not sure how to design a case like this. I will very much appreciate your feedback.

Best regards,
Jorge Maldonado

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: One parent record with 3 possible child records
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox