From: Mitch Vincent <mitch@venux.net>
To: pgsql-sql@postgresql.org
To: Brian C. Doyle <bcdoyle@mindspring.com>
Subject: Re: Multiple Index's
Date: Thu, 21 Sep 2000 10:28:18 -0700
Message-ID: <009401c023f1$5561b0d0$0200000a@doot> (raw)
References: <5.0.0.19.2.20000921130926.02c2ad30@pop>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: mitch@venux.net, bcdoyle@mindspring.com
Subject: Re: Multiple Index's
In-Reply-To: <009401c023f1$5561b0d0$0200000a@doot>
References: <5.0.0.19.2.20000921130926.02c2ad30@pop> <009401c023f1$5561b0d0$0200000a@doot>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox