-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/16/07 17:25, Chris Browne wrote:
> [EMAIL PROTECTED] (Vladimir Zelinski) writes:
>> I tried function now(),current_timestamp() but all of
>> them behave similar.
>>
>> I don't believe that it's bug, probably it's a feature
>> of the postgreSql database.
>
> Indeed, that is intentional. CURRENT_TIMESTAMP and NOW() return the
Ooooh, is that Standard Behavior?
Is there a standard definition for CURRENT_TIMESTAMP?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFF1k91S9HxQb37XmcRAqFsAKCMI+xzFxig2XMDPcsWcRMfToOJ/QCffWwO
iLBhZIc3jGp2VWwVSxW7hRQ=
=RTIl
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
