PHP/MySQL Design Question

[Supernova9]

Ok,

I'm not new to databases, but I am new to mySQL.

To sort of learn the ropes I'm trying to design a basic calendar system, which has 3 tables.

User, Location and Event.

The users create events which take place at one of a number of locations. That will be the relational part, but what I don't know is, how do I create said relationships? It's not like access, I don't have a lookup wizard field type

[meglamaniac]

When you say "create the relationships" what exactly do you mean?
Link the tables in some way so that altering something in one alters fields in another, or what?

[Supernova9]

Originally Posted by meglamaniac

When you say "create the relationships" what exactly do you mean?
Link the tables in some way so that altering something in one alters fields in another, or what?

Say I create a location of "pub", and that has location_id 1,

A user then creates event "piss-up", and wants to set that as taking place in the pub.

I want them to be able to select "pub" from a list of options, and then when they select that, have 1 (the location id of the pub) put into the location field on the events table.

Am I right in thinking this is something I'd be coding in php rather than in the actual design of the database?

[xtothez]

You'd use the pub table to generate a html selection box with php*, using the pub name as the options, with the id as the actual values sent. Then insert that into the events.
If you're looking to enforce referential integrity (making sure one table correctly references the information in another, like in access above), you may be out of luck, as MySQL doesn't support foreign keys in a default setup. Although on this level, you don't really need that if you're only allowing input from a limited set of values anyway.

*Select * from location, then while() through the list printing an <option> for each.

[Supernova9]

Originally Posted by xtothez

You'd use the pub table to generate a html selection box with php*, using the pub name as the options, with the id as the actual values sent. Then insert that into the events.
If you're looking to enforce referential integrity (making sure one table correctly references the information in another, like in access above), you may be out of luck, as MySQL doesn't support foreign keys in a default setup. Although on this level, you don't really need that if you're only allowing input from a limited set of values anyway.

*Select * from location, then while() through the list printing an <option> for each.

Thanks.

[[coza]]

dont think calander is the sort of thing u wanna start on iff yer n00b

[pablissimo]

A calendar isn't a particular complex thing to implement. In fact on the contrary, I think that it's a great idea for learning; things that actually 'do' something when you finish them are infinitely more interesting than random 'SELECT * FROM...' snippets as you try and figure out what goes where and make it much more likely that you'll both persevere and that you'll endevour to go that little bit further to learn.

[xtothez]

Ignore coza.
Usual trolling, and still not very good at it.

[pablissimo]

I thought I'd try shooting him down with logic and reason though =(