From: Mark Volpe <volpe.mark@epamail.epa.gov>
To: Brian C. Doyle <bcdoyle@mindspring.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Multiple Index's
Date: Thu, 21 Sep 2000 13:29:19 -0400
Message-ID: <39CA456F.CB851388@epamail.epa.gov> (raw)
References: <5.0.0.19.2.20000921130926.02c2ad30@pop>
CREATE TABLE user_info(user_id name, entry_date date, info text);
CREATE UNIQUE INDEX user_info_key ON user_info(user_id, entry_date);
"Brian C. Doyle" wrote:
>
> Hello all,
>
> How would I prevent a user from submitting information to a table once they
> have already done so for that day. 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.
>
> I am looking for something like insert user_id, date, info where user_id
> and date are not the same... does that make sense?
>
> Brian C. Doyle
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: volpe.mark@epamail.epa.gov, bcdoyle@mindspring.com
Subject: Re: Multiple Index's
In-Reply-To: <39CA456F.CB851388@epamail.epa.gov>
References: <5.0.0.19.2.20000921130926.02c2ad30@pop> <39CA456F.CB851388@epamail.epa.gov>
* 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