Re: Can't figure out how to use now() in default for tsrange column (PG 9.2)
| От | Alban Hertroys |
|---|---|
| Тема | Re: Can't figure out how to use now() in default for tsrange column (PG 9.2) |
| Дата | |
| Msg-id | CAF-3MvPByCKiA2hf+TBbBjnrRJ91wt5asAnVo=qz=KZGAj+Jpw@mail.gmail.com обсуждение исходный текст |
| Ответы |
Re: Can't figure out how to use now() in default for tsrange
column (PG 9.2)
Re: Can't figure out how to use now() in default for tsrange column (PG 9.2) |
| Список | pgsql-general |
>> BTW, that second value looks a whole lot like a poorly thought out >> substitute for 'infinity' ... >> regards, tom lane > > That's certainly an interesting comment and I'm open to suggestions! The > original db has two columns (from_timestamp, to_timestamp). I don't go for > NULL in the to_timestamp column. Alternatively, a timestamp very, very far > in the future can throw off query planners. Tom is telling you that there is a special "timestamp" 'infinity': alter table the_table alter column the_column set default tsrange(now()::timestamp without time zone, 'infinity'::timestamp without time zone); -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest.
В списке pgsql-general по дате отправления: