public inbox for [email protected]
help / color / mirror / Atom feed6.8.5: Location of CURRENT_DATE unclear
4+ messages / 2 participants
[nested] [flat]
* 6.8.5: Location of CURRENT_DATE unclear
@ 2003-04-10 02:44 Curt Sampson <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Curt Sampson @ 2003-04-10 02:44 UTC (permalink / raw)
To: pgsql-docs
In table 6-18 the 7.3 documentation, it describes the CURRENT_DATE
function as returning "today's date." Section 6.8.4 mentions
CURRENT_DATE again, but does not describe what location is used to
determine the current date. Does this return the current date as of now,
UTC, or the current date in the local timezone?
cjs
--
Curt Sampson <[email protected]> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: 6.8.5: Location of CURRENT_DATE unclear
@ 2003-04-11 20:34 Tom Lane <[email protected]>
parent: Curt Sampson <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Tom Lane @ 2003-04-11 20:34 UTC (permalink / raw)
To: Curt Sampson <[email protected]>; +Cc: pgsql-docs
Curt Sampson <[email protected]> writes:
> In table 6-18 the 7.3 documentation, it describes the CURRENT_DATE
> function as returning "today's date." Section 6.8.4 mentions
> CURRENT_DATE again, but does not describe what location is used to
> determine the current date. Does this return the current date as of now,
> UTC, or the current date in the local timezone?
The latter, as you could easily have found by experiment.
regression=# show timezone;
TimeZone
----------
EST5EDT
(1 row)
regression=# select now(), current_date;
now | date
------------------------------+------------
2003-04-11 16:32:59.84755-04 | 2003-04-11
(1 row)
regression=# set timezone to 'JST-9';
SET
regression=# select now(), current_date;
now | date
-------------------------------+------------
2003-04-12 05:33:19.119802+09 | 2003-04-12
(1 row)
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: 6.8.5: Location of CURRENT_DATE unclear
@ 2003-04-12 03:42 Curt Sampson <[email protected]>
parent: Tom Lane <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Curt Sampson @ 2003-04-12 03:42 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: pgsql-docs
On Fri, 11 Apr 2003, Tom Lane wrote:
> Curt Sampson <[email protected]> writes:
> > In table 6-18 the 7.3 documentation, it describes the CURRENT_DATE
> > function as returning "today's date." Section 6.8.4 mentions
> > CURRENT_DATE again, but does not describe what location is used to
> > determine the current date. Does this return the current date as of now,
> > UTC, or the current date in the local timezone?
>
> The latter, as you could easily have found by experiment.
In fact, I did find that out by experiment. My real question, I guess,
is "is there some good reason not to have this information in the
documentation?" (In fact, I'm sure the answer is "no," so more the real
question is, "Is my whinging enough to get someone to add it, or do I
have to get off my lazy ass and submit a patch?")
cjs
--
Curt Sampson <[email protected]> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: 6.8.5: Location of CURRENT_DATE unclear
@ 2003-04-12 04:16 Tom Lane <[email protected]>
parent: Curt Sampson <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: Tom Lane @ 2003-04-12 04:16 UTC (permalink / raw)
To: Curt Sampson <[email protected]>; +Cc: pgsql-docs
Curt Sampson <[email protected]> writes:
> On Fri, 11 Apr 2003, Tom Lane wrote:
>> The latter, as you could easily have found by experiment.
> In fact, I did find that out by experiment. My real question, I guess,
> is "is there some good reason not to have this information in the
> documentation?" (In fact, I'm sure the answer is "no,"
Certainly.
> so more the real
> question is, "Is my whinging enough to get someone to add it, or do I
> have to get off my lazy ass and submit a patch?")
If you submit a doc patch, it'll get done ;-).
Seriously, the docs are all too much written by people who already knew
the answers. I like doc patches from people who found something out the
hard way, because they tend to put the info where they expected to find
it --- which isn't necessarily where the original developer thought to
document it, but *is* likely to be where other users would look.
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2003-04-12 04:16 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-04-10 02:44 6.8.5: Location of CURRENT_DATE unclear Curt Sampson <[email protected]>
2003-04-11 20:34 ` Tom Lane <[email protected]>
2003-04-12 03:42 ` Curt Sampson <[email protected]>
2003-04-12 04:16 ` Tom Lane <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox