Hello,
I tend to do either what Hardy suggested depending on the needs of your
database. If the trouble ticket table is to be associated with both
faculty and staff, and that fac/staff can have more than one trouble
ticket I like to create a relational table.
To do this you create a separate table with to fields, one for the id for
the faculty-table and the other with the id for the trouble ticket-table
(and then one for staff..)
Then to see if a faculty member has a trouble ticket, just select from the
relational-fac table 'where faculty-id = 'id''.
I can explain further if I didn't quite explain myself good enough :)
Go with what you prefer and stick with it :)
Atle
On Mon, 5 Feb 2001, Chris Toth wrote:
>
>
> I'm having a extremely hard time grasping the concept of multiple tables. So
> far, I've been using just one table when designing a database. But now I
> have to design a database for a trouble-ticket system for our department.
> I've written out the design of the tables, but the part I don't understand
> is how the tables relate to each other. Do I need to use foreign keys? But
> if I do, I thought MySQL didn't support foreign keys?
>
> BTW, I've read most of the O'rielly mSQL/MySQL book and couldn't find my
> answers.
>
> Just in case it matters, I'm going to have one table full of faculty info,
> one of staff info, one for the trouble ticket itself, and possibly one for
> actions performed on the trouble ticket.
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
