I realized that as soon as I hit Send - doh! :)
Jonathan Hilgeman wrote:
> Actually,
> He should be using three. While one company could use many services, you
> might also have other companies that offer the same service. So there should
> be 3 tables to allow a many-to-many relationship. See my e-mail response to
> him.
>
> - Jonathan
>
> "Chris Hobbs" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>
>>I won't add to the code suggestions already given, but I will share one
>>thought about your tables - you absolutely _should_ be using two. Any
>>given company can have from one service to thousands (take GE,
>>everything from light bulbs to cruise missiles :). The only way to
>>capture that data effectively is in two tables.
>>
>>Andrius Jakutis wrote:
>>
>>
>>
>>>Can you help me? I know that for this example its better to use one
>>>
> table,
>
>>>not two, but I am just learning..
>>>
>>
>>--
>>Chris Hobbs Silver Valley Unified School District
>>Head geek: Technology Services Coordinator
>>webmaster: http://www.silvervalley.k12.ca.us/~chobbs/
>>postmaster: [EMAIL PROTECTED]
>>
>>
>
>
>
--
Chris Hobbs Silver Valley Unified School District
Head geek: Technology Services Coordinator
webmaster: http://www.silvervalley.k12.ca.us/~chobbs/
postmaster: [EMAIL PROTECTED]
--
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
