If when someone comes down the line saying 'I want to know x info on all
brands from this year' wouldn't it be more efficient to be selecting that
information based on an ID than it would a date time field? I do not have
specific numbers to prove that theory. Has anyone out there had experience
with such a thing?
At 02:14 PM 06/26/2001 -0700, you wrote:
>Nope, I'm suggesting the same thing as Jeff Houser suggested with one
>exception. Instead using a lookup table for years, I suggest just using a
>column labled "ModelYear" and using the 4-digit year. Additionally, I would
>format that field as a Date/Time field rather than a numerical or text field
>so that you can perform proper Date calculations use proper Between search
>limiters.
>
>Lookup Tales:
>Brand (BrandID, otherbrandinfo)
>Model (ModelID, othermodelinfo)
>
>Intersection table:
>BrandYearModel (BrandID {INT, fk brand.brandid}, YearID {date/time}, ModelID
>{INT, fk model.modelid})
>
>---mark
>
>------------------------------------
>Mark Warrick - Fusioneers.com
>Personal Email: [EMAIL PROTECTED]
>Business Email: [EMAIL PROTECTED]
>Phone: 714-547-5386
>Efax: 801-730-7289
>Personal URL: http://www.warrick.net
>Business URL: http://www.fusioneers.com
>ICQ: 125160 / AIM: markwarric
>====================================
>
> > -----Original Message-----
> > From: Jeff Fongemie [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, June 26, 2001 2:11 PM
> > To: CF-Talk
> > Subject: Re: Simple Database Structure Question, Flat or Relational?
> >
> >
> > Mark, are you suggesting one flat table?
> >
> > Jeff Fongemie
> >
> > "Mark Warrick" <[EMAIL PROTECTED]> wrote in message
> > news:<[EMAIL PROTECTED]>...
> > > That's proper database design, but don't you think you're
> > pushing it a bit?
> > > I mean, there are only so many years and year numbers never
> > change. I think
> > > it would be just as appropriate to just use the 4-digit year in
> > the lookup
> > > (BrandYearModel) table, and would doing that speed up the
> > queries a little
> > > bit.
> > >
> > > ---mark
> > >
> > > ------------------------------------
> > > Mark Warrick - Fusioneers.com
> > > Personal Email: [EMAIL PROTECTED]
> > > Business Email: [EMAIL PROTECTED]
> > > Phone: 714-547-5386
> > > Efax: 801-730-7289
> > > Personal URL: http://www.warrick.net
> > > Business URL: http://www.fusioneers.com
> > > ICQ: 125160 / AIM: markwarric
> > > ====================================
> > >
> > > > -----Original Message-----
> > > > From: Jeffry Houser [mailto:[EMAIL PROTECTED]]
> > > > Sent: Tuesday, June 26, 2001 10:13 AM
> > > > To: CF-Talk
> > > > Subject: Re: Simple Database Structure Question, Flat or Relational?
> > > >
> > > >
> > > >
> > > >
> > > > I think I will set it up this way:
> > > >
> > > > These tables are no-brainers:
> > > > Brand (BrandID, otherbrandinfo)
> > > > Year (YearID, year)
> > > > Model (ModelID, othermodelinfo)
> > > >
> > > > The intersection tables can get a little confusing. I would set
> > > > it up this
> > > > way, with one Intersection table:
> > > >
> > > > BrandYearModel (BrandID, YearID, ModelID)
> > > >
> > > > Given the brand, you can get the years. Given the brand and
> > > > year you can
> > > > get the models.
> > > >
> > > >
> > > > At 07:23 AM 06/26/2001 -0400, you wrote:
> > > > >Hello cf-talk,
> > > > >
> > > > > I need to design a "product compatability" guide for a client. I'm
> > > > > looking for the best database setup.
> > > > >
> > > > > 1. We need a drill down feature for product brand,
> > product year, and
> > > > > product model. A user will first choose the Brand, then the year,
> > > > > then the model.
> > > > >
> > > > > 2. I'll use cfselect to make the drop down boxes that
> > > > > will populate based on the previous selection. Choose a
> > brand, then
> > > > > the years available will show in a CFSELECT on the following page,
> > > > > then models on the next page ect.
> > > > >
> > > > > So, I have a relational database one to many for Models to Brands
> > > > > respectively, but what would be the best way to add in model year.
> > > > > Do I add a new table just for model years, and have that
> > many to one
> > > > > with Brands, and have models be many to one with year?
> > > >
> > > > > Or, just have the year as another field in the Model table?
> > > > >
> > > > > Any advice here to save me from stumbling through the above
> > > > options to see
> > > > > what works best would be very much appreciated.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >Best regards,
> > > > > Jeff Fongemie mailto:[EMAIL PROTECTED]
> > > > >------------------------
> > > > >Internet Guns For Hire
> > > > >(603) 356-0768
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
