Re: Range Types: empty ranges
| От | Robert Haas |
|---|---|
| Тема | Re: Range Types: empty ranges |
| Дата | |
| Msg-id | AANLkTinRW6N3yWpGBggq9ksfdTveFg0NeBNtFR=essiE@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Range Types: empty ranges ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
| Ответы |
Re: Range Types: empty ranges
|
| Список | pgsql-hackers |
On Fri, Feb 11, 2011 at 1:50 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> Josh Berkus <josh@agliodbs.com> wrote:
>
>> if I, in one of my applications, accidentally defined something
>> as having the range '('15:15:00','15:15:00')', I would *want* the
>> database to through an error and not accept it.
>
> I can agree with that, but I think that range '[15:15:00,15:15:00)'
> should be valid as a zero-length range between, for example,
> '[15:00:00,15:15:00)' and '[15:15:00,15:30:00)'.
How would that actually work? I kind of agree with Josh: I'd be
inclined to make the type input function boot such constructs at the
door.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: