Okay, hopefully I'm somewhat clearer today.  I doubt
it but the effort is going to be made regardless.

First off, Rhino I read through your last post,
regarding the phone number table.  Yes I defintely
understand it and see how each situation may warrant a
different design.  You gave scenarios for both.  Very
clear.  Slowly it's sinking in.  For example, I had a
"states" table, but I was going to accept Cities to be
text input.  Very wrong.  I came up with a very solid
list of major cities in ever state.  For redundancy
I'll probably add metro areas, and quadrants of some
sort.  Each of course with their own tables.  I see
this is as a very good place to implement the M2M.
Agreed ?

Now, back to my title list.   There are a number of
business reasons why I'm forgoing the title table and
even tracking titles in a seperate place.  After
looking through Monster and CareerBuilders and the
similar others, there just isn't enough proof that it
would make sense.  Some of the titles I've seen are
combinations of things totally unrelated, others are
comppletely vauge.  While there are standards and
atypical job titles, there are also a huge number that
are not.  For instance, I applied for a position a few
months back titled, Senior Sales Representative 12.  I
thought I was an eleven, so I went for it anyone.  All
reasoning aside. Seriously though, I just believe
after review that it makes no business sense for that
design.  If I was running an internal job site for 1
company, then yes perhaps. There is a table though of
industries and fields.  

Hope this explains my mutterings the other day.

Also, yes I would like to share my design at some
point for some critique. It maybe slightly premature,
but I will defintely ping you when I'm ready.

Thank you,
Stuart

--- Rhino <[EMAIL PROTECTED]> wrote:

> I guess I'll have to wait until you've had a chance
> to mull the whole note
> over ;-)
> 
> I really don't know what you're saying. I can't
> think of anything I said
> that would have discouraged you from creating the
> association table.
> Certainly the number of columns in the table
> shouldn't discourage you since
> there are typically only two columns and they are
> usually both short codes.
> 
> The number of rows *may* be a concern though; if you
> have a lot of job
> titles and a keep track of every job every member
> has had, you could end up
> with a lot of rows. Maybe that's your concern.
> 
> In any case, I hope you can explain what you are
> going to do instead of the
> association table if you have definitely abandoned
> it. Maybe we can critique
> that design for you and help you improve it or at
> least avoid the most
> common pitfalls.
> 
> Rhino
> 
> 
> 
> 
> ----- Original Message ----- 
> From: "Stuart Felenstein" <[EMAIL PROTECTED]>
> To: "Rhino" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>; "Stuart Felenstein"
> <[EMAIL PROTECTED]>
> Sent: Friday, August 27, 2004 4:47 PM
> Subject: Re: Many to Many: Does this make sense ?
> 
> 
> > Let me answer the first part now and then continue
> > reading.
> >
> > You absolutely gave me some great ideas /
> examples.
> > I understand it very well now.  I'm abandoning it
> > solely because creating that association list -1)
> may
> > take forever and still come up way short 2)I see
> how
> > others have implemented the same type of
> application
> > and have not provided specific job title
> allocation.
> >
> > I hope that gets you settled back again!
> > Stuart
> > --- Rhino <[EMAIL PROTECTED]> wrote:
> >
> > > My replies are interspersed below.
> > >
> > > Rhino
> > >
> > > ----- Original Message ----- 
> > > From: "Stuart Felenstein" <[EMAIL PROTECTED]>
> > > To: "Rhino" <[EMAIL PROTECTED]>;
> > > <[EMAIL PROTECTED]>
> > > Cc: <[EMAIL PROTECTED]>; "Stuart Felenstein"
> > > <[EMAIL PROTECTED]>
> > > Sent: Friday, August 27, 2004 3:05 PM
> > > Subject: Re: Many to Many: Does this make sense
> ?
> > >
> > >
> > > > Now I am totally clear on it! Took a few
> > > reiterations
> > > > but I'm there.  Even more I'm going to abandon
> the
> > > > idea of titles.
> > >
> > > I was breathing a sigh of relief that we'd
> finally
> > > articulated the idea
> > > clearly enough. But now I'm not so sure....
> > >
> > > What do you mean you are going to "abandon the
> idea
> > > of titles"?
> > >
> >
> 
> 


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to