I'm trying to get a project going which is basically converting a
price catalog into a database, however, going over the printed catalog,
basically this is what it looks like:
service_category_1
description (text)
service_1
description (text)
prices (integers)
notes (text)
service_2
description (text)
prices (integers)
notes(text)
service_3
etc...
service_category_2
description (text)
service_1
description (text)
prices (integers)
notes (text)
service_2
etc...
So I'm trying to figure out what is the best type of structure to
build. Should I make a separate database for each individual category,
and put the different services under that? Or should I have different
DBs for each service?
Also, I need to make this in some way that it's easy for others to
update (although I think this will lean more towards the interface
programming than the DB itself)
Any suggestions? Or better yet, any book recommendations on DB
structures and what not? I plan on getting MySQL (
http://www.amazon.com/exec/obidos/ASIN/0735709211/ref=wl_em_to_i4 ), but
I'm not sure that's enough as I've never done much with MySQL aside from
your very (VERY) basic DB setup, and simple tables and queries.
AMK4
--
W |
| I haven't lost my mind; it's backed up on tape somewhere.
|____________________________________________________________________
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130
SysAdmin / Websmith . 800.441.3873 x130
Photo Craft Laboratories, Inc. . eFax 248.671.0909
http://www.pcraft.com . 3550 Arapahoe Ave #6
.................. . . . . Boulder, CO 80303, USA
---------------------------------------------------------------------
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
