Re: [Sqlalchemy-users] postgresql now function

OK then this fix is committed in 1072, hardcodes against the list below (case-insensitively) for "non-parenthesis" operation.On Mar 1, 2006, at 2:12 PM, Jonathan Ellis wrote:On 3/1/06, Michael Bayer <[EMAIL PROTECTED]> wrote: this is very concerning, since other Postgresql functions only workif you

Re: [Sqlalchemy-users] postgresql now function

SELECT current_date + interval '3 days' as Saturday saturday - 2006-03-04 00:00:00 But in MS-SQL, it's SELECT dateadd(d, 3, getdate()) as Saturday Saturday -- 2006-03-04 14:16:19.060 Should SA even

Re: [Sqlalchemy-users] postgresql now function

On 3/1/06, Michael Bayer <[EMAIL PROTECTED]> wrote: this is very concerning, since other Postgresql functions only workif you *dont* put parenthesis, like "current_date".  the parenthesislogic is currently based on the existence of arguments and wasexplicitly added for that reason. In that respect,

Re: [Sqlalchemy-users] postgresql now function

For better or worse, PG tries to track the SQL standard, and the non-parametrized version of current_date & etc. are taken from that. In fact, post 7.2 PG in fact do take an optional parameter that gives the precision to use for fractional seconds:     SELECT current_time timez -

Re: [Sqlalchemy-users] postgresql now function

this is very concerning, since other Postgresql functions only work if you *dont* put parenthesis, like "current_date". the parenthesis logic is currently based on the existence of arguments and was explicitly added for that reason. so, we will either have to add a flag to "func" to indica