Search Postgresql Archives

Re: Variable constants ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Variable constants ?
From: Rich Shepard <rshepard@xxxxxxxxxxxxxxx>
Date: Fri, 16 Aug 2019 05:50:08 -0700 (PDT)
In-reply-to: <11025034d9e2c2b5e0316aa1f80dfe68@swisspug.org>
References: <20190815205657.GA2593@panix.com> <alpine.LNX.2.20.1908151422480.13052@salmo.appl-ecosys.com> <11025034d9e2c2b5e0316aa1f80dfe68@swisspug.org>
User-agent: Alpine 2.20 (LNX 67 2015-01-07)

On Fri, 16 Aug 2019, Charles Clavadetscher wrote:

Another way to keep a history is using a daterange instead of two columns forstart and end date. Something like
create table labor_rate_mult (
 rate 		real primary_key,
 validity	daterange not null
)


Charles,

Just out of curiosity, what is the range for a rate that is still current?
Does it change every day?

Regards,

Rich

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Variable constants ?
  - From: Charles Clavadetscher

References:
- Variable constants ?
  - From: stan
- Re: Variable constants ?
  - From: Rich Shepard
- Re: Variable constants ?
  - From: Charles Clavadetscher

Prev by Date: ODBC Driver Version for PostgreSQL 11.3
Next by Date: Re: Variable constants ?
Previous by thread: Re: Variable constants ?
Next by thread: Re: Variable constants ?
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux