To elaborate a little more,

In essence, the options and the option groups will be added to the database by an admin,
the products will be added by admins and employees alike.

When an employee goes to add a product, I want them to be able to choose from a dropdown or a table with names and radio buttons or checkboxes to select the options for that product.
Selecting the option will corolate their option groups when selected.

The productID, optionID and optionGroupID will be stored in the productoptions table when the product gets submitted.

That simple. Or I think that simple.. :)


On Apr 30, 2010, at 2:59 PM, David Murphy wrote:

-----Original Message-----
From: Karl DeSaulniers []
Sent: Friday, April 30, 2010 1:50 PM
Subject: Re: [PHP-DB] grabbing from multiple tables

No, please confuse me. I need to know this stuff.

@Peter thanks for that introduction to foreign keys. Since my
productoptions table is based off of items in products, optionGroups
and options, would I use foreign keys for this?

@DZvonko Thanks for trying to protect me, but I am a big boy. :) Do
you have an example of how this JOIN works? Since my productoptions
table is based off of items in products, optionGroups and options,
would I use JOIN for this? And how?

I am looking for the quickest and easiest obviously, but not against
learning the longer and harder.
I just really wanted to know how to use the foreign key in a real
If JOIN is a more viable solution, I'm all ears.

Any examples or tutorials someone can send me?



On Apr 30, 2010, at 6:41 AM, DZvonko Nikolov wrote:


don't confuse the guy. Just use JOIN clause and you will be fine.
Check for the right syntax and don't complicate more. He said he
is quite new, so discuss about foreign keys will only confuse him.

Use JOIN and pure SQL and you will be fine.


--- On Fri, 4/30/10, Peter Lind <> wrote:

From: Peter Lind <>
Subject: Re: [PHP-DB] grabbing from multiple tables
To: "Karl DeSaulniers" <>
Cc: "" <>
Date: Friday, April 30, 2010, 12:31 PM

On 30 April 2010 12:26, Karl DeSaulniers <> wrote:
Thanks Peter.
So what is the logic behind foreign keys? Why use them?

Constraints. When using, for example, the InnoDB engine in MySQL, you
can set foreign key fields on tables. These ensure that your record
will always be bound to a proper record in the connected table - so,
for instance, you won't find yourself in the situation that you have
deleted a record from table1 but table2 still references the table1
record. Also, they're very useful for tying models together
automatically, as you can deduce relationships between models by
foreign keys, for instance (this is simplified but covers a lot of


WWW: /
BeWelcome: Fake51
Couchsurfing: Fake51

PHP Database Mailing List (
To unsubscribe, visit:

Karl DeSaulniers
Design Drumm

Karl I am finding it hard to grasp why you are doing things this way why
not  have

A products table with enums for size/color? Then on the edit page, you can read the product tables schema to get the enum options and explode
them in PHP...


$tData=$db->QuerryToArray("desc products");
$tSizes = explode(",",$tData['Sizes']);
$tColors = explode(",",$tData['Colors']);

Then in the  post system...

$ProductSettings=$db-QueryToArray("select * from products where

Foreach ($NewProductSettings as $Setting=>$Value)
  If($ProdcutSettings[$Setting] !== $Value)
($db->UpdateFromArray("products",$tUpdates,"id='{$this- >CurrentProductID}'")

Since the table would be using an ENUM or SET the column size is very
small  but also very granular.

I think breaking the tables apart is actually more complicated than its
worth for your needs.

Karl DeSaulniers
Design Drumm

PHP Database Mailing List (
To unsubscribe, visit:

Reply via email to