Manfred Koizar <[EMAIL PROTECTED]> writes:
> And one last thought: There are applications out there that are not
> written for one specific database backend. Having to replace
> CURRENT_TIMESTAMP by PG-specific now('statement') is just one more
> pain in trying to be portable across different backends.
Based on this discussion, it seems any application that depends on a
specific behavior of CURRENT_TIMESTAMP is going to have portability
problems anyway. Even if we did change CURRENT_TIMESTAMP to match
now('statement'), it would not act exactly like anyone else's.
regards, tom lane
---------------------------(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
