Well, every resort will have a max price, a min price,
one location, and many activities. So you can get away
with three tables.
resorts resort_activities activities<
-------- ---------- ----------
resort_id* resort_id activity_id
name activity_id description
location
This isn't too bad for a start. I personally recommend
something like postgresql for this. DBD::CSV is good, but
I don't know how it does with multi-table relations.
You could really do all of this with one table instead of
three, but your database wouldn't be 'normalized'. Look
into the concept of 'normalization' before you design
anything that needs to grow to any useful size.
--Gabriel
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
