On Mon, Oct 13, 2008 at 04:29:45PM +, Matthew Wilson wrote:
> I track employee qualifications in one table and I track job
> requirements in another table. A job requires zero-to-many
> qualifications, and for an employee to be qualified for that job, the
> employee must have ALL the requireme
On Mon, Oct 13, 2008 at 1:11 PM, Richard Broersma
<[EMAIL PROTECTED]> wrote:
> On Mon, Oct 13, 2008 at 9:29 AM, Matthew Wilson <[EMAIL PROTECTED]> wrote:
> I don't have the book in front of me at the moment, but I remember
> this exact problem and a unique solution using a schema redesign
> around
On Mon, Oct 13, 2008 at 9:29 AM, Matthew Wilson <[EMAIL PROTECTED]> wrote:
> Any advice? I wonder if this is a sign of a bad design, or maybe if
> there's some nicer SQL techniques I could use.
I don't have the book in front of me at the moment, but I remember
this exact problem and a unique sol
I track employee qualifications in one table and I track job
requirements in another table. A job requires zero-to-many
qualifications, and for an employee to be qualified for that job, the
employee must have ALL the requirements.
For example, In my job requirements table, I record that a nurse m
