|
PolarBear -> RE: Database Question (9/3/2008 2:01:01 PM)
|
Hi, No, use the same database for everything, especially if it will be joined together. Use different tables though. Always remember the principle of normalization. If you don't, you will regret it later. It basically means that the same piece of data should never be stored twice. For example, do NOT have a table like this: book name, book store name Instead have a table 'books' with a field 'id' (type auto_increment) and the title and description as text. Another table 'bookstores' also with an auto_increment id, bookstore name, address, whatever as text. Then a table 'bookatstore' or whatever with each row containing the ID of a book and the ID of a store. About forms, that's the fun of web programming. It can be a bit tedious. Basically your server script has to parse the contents of the form variables, then construct an appropriate SQL database command inserting all the values. If the form is for editing a record, it first needs to SELECT the current contents, put them in the form, then on submit you need to construct an UPDATE command.
|
|
|
|