From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Oliver Kohll - Mailing Lists <oliver(dot)lists(at)gtwm(dot)co(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: [pgsql-general] Daily digest v1.9081 (14 messages) |
Date: | 2009-06-11 14:50:21 |
Message-ID: | 20090611145021.GA5000@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jun 08, 2009 at 08:08:02PM +0100, Oliver Kohll - Mailing Lists wrote:
> On 8 Jun 2009, at 17:23, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>
>>>> Is there a way when creating a table to limit it to one row? That
>>>> is,
>>>> without using a stored procedure?
>>>>
>>>> I searched the documentation, but didn't find anything.
>>>>
>>>
>>>
>>> CREATE TABLE x (...);
>>>
>>> CREATE UNIQUE INDEX x_only_one_row ON ((1));
>>
>> very clever :D
>>
>> merlin
>
> To clever for me, I don't understand what's going on and can't
> replicate it in my 8.3. Any expansion?
This should actually read:
CREATE UNIQUE INDEX x_only_one_row ON x((1));
This creates a unique expressional index on the table. This
expression evaluates as true only in cases where the table has at most
one row, independently of what the possible row contains.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Broersma | 2009-06-11 14:59:26 | Re: When to use cascading deletes? |
Previous Message | Merlin Moncure | 2009-06-11 14:26:46 | Re: help with data recovery from injected UPDATE |