2009/6/9 Brandon Metcalf <brandon@xxxxxxxxxxxxxxxxxx>: > > 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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
