Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 752347" data-attributes="member: 82144">Looks like you're well on your way! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />Yep, that's correct. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Pretty much. The channelType needs to stay as 0, but aside from that what you're doing is fine.idChannel and idTuning are the primary keys on each table. They have to be unique (ie. you can't have two TuningDetail records with the same idTuning... and the same for Channel with idChannel), but other than that you can make them whatever you like. Sequential is probably best and easiest. Note that there is one important thing to remember: the idChannel column in the TuningDetail has to match the idChannel of the Channel record that the TuningDetail is related to. That's a standard foreign key reference...</blockquote>

[QUOTE="mm1352000, post: 752347, member: 82144"] Looks like you're well on your way! :D Yep, that's correct. :) Pretty much. The channelType needs to stay as 0, but aside from that what you're doing is fine. idChannel and idTuning are the primary keys on each table. They have to be unique (ie. you can't have two TuningDetail records with the same idTuning... and the same for Channel with idChannel), but other than that you can make them whatever you like. Sequential is probably best and easiest. Note that there is one important thing to remember: the idChannel column in the TuningDetail has to match the idChannel of the Channel record that the TuningDetail is related to. That's a standard foreign key reference... [/QUOTE]

Verification