Re: Check for no more than two entries of each value in a column?
From: ddf <oratune_at_msn.com>
Date: Fri, 17 Apr 2009 12:40:32 -0700 (PDT)
Message-ID: <48b8d18b-8f15-459f-ba68-73e3981bbebb_at_r34g2000vba.googlegroups.com>
On Apr 17, 1:53 pm, Shakespeare <what..._at_xs4all.nl> wrote:
> ddf schreef:
>
> > On Apr 17, 12:38 pm, livefreeordie <jpittm..._at_gmail.com> wrote:
> >> Hi,
> > knip knip
> > With the commit inside the procedure you *should* be able to keep to
> > the two nominations maximum per nominator (of course depending upon
> > how active this nomination process can be with multiple users you may
> > have a few slip through the cracks).
>
> > David Fitzjarrell
>
> This could only happen with the same nominator voting in different
> sessions at the same time....
>
> Shakespeare
Date: Fri, 17 Apr 2009 12:40:32 -0700 (PDT)
Message-ID: <48b8d18b-8f15-459f-ba68-73e3981bbebb_at_r34g2000vba.googlegroups.com>
On Apr 17, 1:53 pm, Shakespeare <what..._at_xs4all.nl> wrote:
> ddf schreef:
>
> > On Apr 17, 12:38 pm, livefreeordie <jpittm..._at_gmail.com> wrote:
> >> Hi,
> > knip knip
> > With the commit inside the procedure you *should* be able to keep to
> > the two nominations maximum per nominator (of course depending upon
> > how active this nomination process can be with multiple users you may
> > have a few slip through the cracks).
>
> > David Fitzjarrell
>
> This could only happen with the same nominator voting in different
> sessions at the same time....
>
> Shakespeare
Not necessarily. Presume for a moment that members of a nominating committee enter the nominations; in that situation the currently connected user is NOT the nominator. The procedure, as written, accepts both the nominator and the nominee, so it is possible for someone else to process a nomination made by a third party.
The materialized view solution is more elegant.
David Fitzjarrell Received on Fri Apr 17 2009 - 14:40:32 CDT