From a high level, I'd have something set up like so:

destinations:
------------------
id
name
etc

dates:
------------------
id
destination_id
date
etc.

departures:
------------------
id
date_id
time
etc.

arrivals:
------------------
id
date_id
time
etc.


I'd quickly throughout the departure_1, departure_2 idea just because
it makes querying the database a PITA real quick.  If they only have 2
departure times, you have to check for nulls.  You have to
programmatically make sure that departure_1 is earlier than
departure_2, etc.

With the correct indexing, your database would sail through simple
queries required here.


On 3/14/07, Kevin <[EMAIL PROTECTED]> wrote:




Well, to go back to my example, The cruise in april has departure times and
pickup times for each day.  However, all of these are different.



The problem with the db option is that if I had a cruise_time table I would
have to have a number of fields defined for departure_1, departure_2,
departure_3 as well as pickup_1, pickup_2, pickup_3 for each product.  I was
thinking that xml might be helpful because we could have



<date>

                <departure>

                                <time>time1</time>

                                <time>time3</time>

                </departure>

                <return>

                                <time>Time1</time>

                                <time>time2</time>

                                <time>time3</time>

                </return>

</date>



Again, maybe I'm just not approaching the database correctly.  The system is
currently using the db to manage all of the times.  I am trying to find the
easiest and most robust solution.  So XML is out I guess?




Kevin





From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Tim Hoffman
 Sent: Wednesday, March 14, 2007 10:01 PM
 To: 'Dallas/Fort Worth ColdFusion User Group Mailing List'
 Subject: RE: [DFW CFUG] xml, etc.




I'm not quite getting it either. Can you give us a more concrete example?



Tim



 ________________________________


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Marvin Eads
 Sent: Wednesday, March 14, 2007 10:01 PM
 To: Dallas/Fort Worth ColdFusion User Group Mailing List
 Subject: Re: [DFW CFUG] xml, etc.





I had the same thought.  I just figured I didnt quite understand his needs.

 XML is extremely verbose.  Putting that many products with all your hours
and days into XML will result in a huge file.  Large datasets is exactly
what databases are for.

 Maybe you need to be more clear about your logic in thinking XML is a
better choice.  I may just not be getting it.

 Marvin


----- Original Message ----
 From: Marlon Moyer <[EMAIL PROTECTED]>
 To: Dallas/Fort Worth ColdFusion User Group Mailing List
<[email protected]>
 Sent: Wednesday, March 14, 2007 9:47:30 PM
 Subject: Re: [DFW CFUG] xml, etc.


I'm not clear why you think that a database wouldn't be a good place
 to store 8000 products?

 As for xml of that size, unless you read it once and then store it in
 memory, it will be extremely slower than using a db to query the
 information.


 On 3/14/07, Kevin <[EMAIL PROTECTED]> wrote:
 >
 >
 >
 >
 > I think that I have asked this before…if so I must not have received and
 > answer.
 >
 >
 >
 > I have an application that is booking reservations for various cruises.
 > The cruise goes every day but each day has different times.  There is not
 > the ability to simply set up a table for mon, tues, wed, etc. with times.
 > For example, in April, 15 of the days have the same time and the others
all
 > have different times.
 >
 >
 >
 > I was thinking that I would put this in an XML file rather than in the
 > database.  Anyone have any ideas how we would best achieve the
flexibility
 > of storing and serving all of these times?  It seems that XMLParse is not
 > real fast.  One other thing to note….we have 8000 products….this is why I
 > was thinking that we would not store all of this information in a
database.
 >
 >
 >
 > Any help would be appreciated.
 >
 >
 >
 > Thanks,
 >
 >
 >
 > Kevin
 > _______________________________________________
 > Reply to DFWCFUG:
 >   [email protected]
 > Subscribe/Unsubscribe:
 >   http://lists1.safesecureweb.com/mailman/listinfo/list
 > List Archives:
 >     http://www.mail-archive.com/list%40list.dfwcfug.org/
 >   http://www.mail-archive.com/list%40dfwcfug.org/
 > DFWCFUG Sponsors:
 >   www.instantspot.com/
 >   www.teksystems.com/
 >
 >


 --
 "Donnie D's on the backup,
 drug free so put the crack up.
 No need for speed,
 I'm anti d-r-u-g-g-i-e"

 _______________________________________________
 Reply to DFWCFUG:
   [email protected]
 Subscribe/Unsubscribe:
   http://lists1.safesecureweb.com/mailman/listinfo/list
 List Archives:
     http://www.mail-archive.com/list%40list.dfwcfug.org/
   http://www.mail-archive.com/list%40dfwcfug.org/
 DFWCFUG Sponsors:
   www.instantspot.com/
   www.teksystems.com/


_______________________________________________
Reply to DFWCFUG:
  [email protected]
Subscribe/Unsubscribe:
  http://lists1.safesecureweb.com/mailman/listinfo/list
List Archives:
    http://www.mail-archive.com/list%40list.dfwcfug.org/
  http://www.mail-archive.com/list%40dfwcfug.org/
DFWCFUG Sponsors:
  www.instantspot.com/
  www.teksystems.com/




--
"Donnie D's on the backup,
drug free so put the crack up.
No need for speed,
I'm anti d-r-u-g-g-i-e"

_______________________________________________
Reply to DFWCFUG:
 [email protected]
Subscribe/Unsubscribe:
 http://lists1.safesecureweb.com/mailman/listinfo/list
List Archives:
   http://www.mail-archive.com/list%40list.dfwcfug.org/
 http://www.mail-archive.com/list%40dfwcfug.org/
DFWCFUG Sponsors:
 www.instantspot.com/
 www.teksystems.com/

Reply via email to