On Thu, 2005-02-10 at 16:32 +0900, Michael Glaesemann wrote:
> I realize it's a bit late, but it might not be a bad idea to use 
> CURRENT_TIMESTAMP rather than NOW(), as it's per SQL spec.

I can't say I can get very excited about it; someone is free to submit a
patch if they like.


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to