Re: limit table to one row

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: Brandon Metcalf <brandon(at)geronimoalloys(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: limit table to one row
Date: 2009-06-09 15:37:48
Message-ID: 2f4958ff0906090837w7d945027y109573f9615ad369@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2009/6/9 Brandon Metcalf <brandon(at)geronimoalloys(dot)com>:

>
>  CREATE TABLE foo (
>    start  DATE,
>    length VARCHAR(10),
>  );
>
> I need to be able to get one value for each column at any given time.
> Specifically, I need to get a value for start and add the value for
> length to get a time period.  Since your approach would allow more
> than one row, how does it help me?

If you want to store period of time, why store it as varchar ?

just store two rows
create table foo(
n varchar,
val date
);

and store two rows:
"start", now(),
"end", now()+'something '::interval

Wouldn't that do, or is there something I misunderstand ?

The approach with vertical structure, is used when people want to
store some particular state, say - kind of like structure in C, but in
SQL, and they create table for it with all the columns, etc, and have
to limit it to one row.

On the other hand, you could also use unique index on (1) approach
(say if you need more variety of types).

--
GJ

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dimitri Fontaine 2009-06-09 15:45:29 Re: postgres getting slow under heavy load though autivacuum is enabled
Previous Message Brandon Metcalf 2009-06-09 15:24:01 Re: limit table to one row