public inbox for [email protected]  
help / color / mirror / Atom feed
Default Values Section
2+ messages / 2 participants
[nested] [flat]

* Default Values Section
@ 2005-01-04 17:51 Lourival Oliveira <[email protected]>
  2005-02-11 04:32 ` Re: Default Values Section Bruce Momjian <[email protected]>
  0 siblings, 1 reply; 2+ messages in thread

From: Lourival Oliveira @ 2005-01-04 17:51 UTC (permalink / raw)
  To: pgsql-docs

I have a problem reading the "5.3 Default Values" Section of 
Postgresql8.0.0-rc1 documentation. In this section there are nothing about 
using 'now' constant. I think which there are a conflict with a note about 
'now' in section "9.9. Date/Time Functions and Operators" which show the way 
to achieve the desired behavior. See:

5.3. Default Values

...

The default value may be a scalar expression, which will be evaluated 
whenever the default value is inserted (not when the table is created).


9.9. Date/Time Functions and Operators

...

SELECT CURRENT_TIMESTAMP;
SELECT now();
SELECT TIMESTAMP 'now';
Note: You do not want to use the third form when specifying a DEFAULT clause 
while creating a table. The system will convert now to a timestamp as soon 
as the constant is parsed, so that when the default value is needed, the 
time of the table creation would be used! The first two forms will not be 
evaluated until the default value is used, because they are function calls. 
Thus they will give the desired behavior of defaulting to the time of row 
insertion.

I think which a simple reference to any unpredictable behavior must be 
placed here to avoid confusion when anybody don't reach the desired behavior 
when use default values.

What think you about my suggestion?

Wait replies, Tanks.

Lourival Oliveira da Silva

PS: Sorry by my poor English. 





^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Default Values Section
  2005-01-04 17:51 Default Values Section Lourival Oliveira <[email protected]>
@ 2005-02-11 04:32 ` Bruce Momjian <[email protected]>
  0 siblings, 0 replies; 2+ messages in thread

From: Bruce Momjian @ 2005-02-11 04:32 UTC (permalink / raw)
  To: Lourival Oliveira <[email protected]>; +Cc: pgsql-docs


OK, I updated the documentation to add a comment on that line:
	
	SELECT CURRENT_TIMESTAMP;
	SELECT now();
	SELECT TIMESTAMP 'now';  -- incorrect for use with DEFAULT


---------------------------------------------------------------------------

Lourival Oliveira wrote:
> I have a problem reading the "5.3 Default Values" Section of 
> Postgresql8.0.0-rc1 documentation. In this section there are nothing about 
> using 'now' constant. I think which there are a conflict with a note about 
> 'now' in section "9.9. Date/Time Functions and Operators" which show the way 
> to achieve the desired behavior. See:
> 
> 5.3. Default Values
> 
> ...
> 
> The default value may be a scalar expression, which will be evaluated 
> whenever the default value is inserted (not when the table is created).
> 
> 
> 9.9. Date/Time Functions and Operators
> 
> ...
> 
> SELECT CURRENT_TIMESTAMP;
> SELECT now();
> SELECT TIMESTAMP 'now';
> Note: You do not want to use the third form when specifying a DEFAULT clause 
> while creating a table. The system will convert now to a timestamp as soon 
> as the constant is parsed, so that when the default value is needed, the 
> time of the table creation would be used! The first two forms will not be 
> evaluated until the default value is used, because they are function calls. 
> Thus they will give the desired behavior of defaulting to the time of row 
> insertion.
> 
> I think which a simple reference to any unpredictable behavior must be 
> placed here to avoid confusion when anybody don't reach the desired behavior 
> when use default values.
> 
> What think you about my suggestion?
> 
> Wait replies, Tanks.
> 
> Lourival Oliveira da Silva
> 
> PS: Sorry by my poor English. 
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to [email protected] so that your
>       message can get through to the mailing list cleanly
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  [email protected]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073




^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2005-02-11 04:32 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-01-04 17:51 Default Values Section Lourival Oliveira <[email protected]>
2005-02-11 04:32 ` Bruce Momjian <[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