| From: | Brandon Metcalf <brandon(at)geronimoalloys(dot)com> |
|---|---|
| To: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: limit table to one row |
| Date: | 2009-06-09 15:24:01 |
| Message-ID: | Pine.LNX.4.58L.0906091011340.11099@cedar.geronimoalloys.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
g == gryzman(at)gmail(dot)com writes:
g> 2009/6/9 Brandon Metcalf <brandon(at)geronimoalloys(dot)com>:
g> > I'm not sure I follow how this solves the problem.
g> Well, surely if you just need one row, you need single value per key.
g> And that's the, imo , better solution to that problem, than limiting
g> number of rows.
Hm. Maybe I'm looking at the problem incorrectly. I have a situation
where I need a table like
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?
--
Brandon
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grzegorz Jaśkiewicz | 2009-06-09 15:37:48 | Re: limit table to one row |
| Previous Message | G. Allegri | 2009-06-09 15:16:48 | Re: column name gets substitudes inside an execute statement of a trigger function. how to avoid it?! |