From: | "Brian C(dot) Doyle" <bcdoyle(at)mindspring(dot)com> |
---|---|
To: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Multiple Index's |
Date: | 2000-09-21 17:30:02 |
Message-ID: | 5.0.0.19.2.20000921132629.032fdb60@pop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
See if this help
the table has
userid | date | helped_customers
An employ will enter in their userid, the date and how many customer they
helped that day.
What I want to do is prevent the employees from enter the data more than
once a day
At 10:28 AM 9/21/00 -0700, Mitch Vincent wrote:
> > Hello all,
> >
> > How would I prevent a user from submitting information to a table once
>they
> > have already done so for that day.
>
>The best you could probably do is to go back and delete undesired recoords
>at the end of the day because if it is as you said, they've already put the
>information into the database.
>
> > I would need them to be able
> > information on future dates as well as have information in the table from
> > past dates from that user.
>
>Not positive what you mean here but just use a date (or timestamp) column in
>the table to indicate when the record was added.
>
> > I am looking for something like insert user_id, date, info where user_id
> > and date are not the same... does that make sense?
>
>Nope, it doesn't -- at least to me :-)
>
>How about some table structures and some more information, I'm just not
>exactly sure what you'd like to do..
>
>-Mitch
From | Date | Subject | |
---|---|---|---|
Next Message | Webb Sprague | 2000-09-21 18:10:36 | Convert from Seconds-Since-Epoch to Timestamp |
Previous Message | Mark Volpe | 2000-09-21 17:29:19 | Re: Multiple Index's |