...
> Well, I'll take responsibility for fixing that, if you want to spread
> the blame ;-). It's my fault that those routines are marked cachable
> to begin with --- I hadn't dug into which datetime types had "current"
> and which didn't, just marked 'em all noncachable on sight.
I'm happy to d
Thomas Lockhart <[EMAIL PROTECTED]> writes:
> Hmm. Perhaps the definition for CURRENT_DATE should be recast as a call
> to now() (which happens to return timestamp)
Yes, something like date(now()) might be less subject to breakage as we
monkey around with the semantics of literals and implicit co
> I've been looking at the iscachable changes you committed recently,
> and I think a lot of them need to be adjusted still.
Sure. Me too ;)
I changed some for the areas within which I was working, and it did
occur to me that (as you mention below) anything affected as a side
effect of some othe
I've been looking at the iscachable changes you committed recently,
and I think a lot of them need to be adjusted still.
One consideration I hadn't thought of recently (though I think we did
take it into account for the 7.0 release) is that any function whose
output varies depending on the TimeZo
