> Offhand I'd expect the 'now' to be reduced to a timestamp constant
> at the time the view is created.
Hmmm, my assumption had been that the 'now' constant would be evaluated
everytime the underlying SELECT was build by the planner.
> although personally I'd not feel very comfortable with the id
Glen Eustace <[EMAIL PROTECTED]> writes:
> The view is defined to be;
> CREATE VIEW domain_registry AS
>SELECT *
> FROM domain_registry_history
> WHERE tstamp > 'now';
Offhand I'd expect the 'now' to be reduced to a timestamp constant
at the time the view is created.
Perhaps you
Hi,
I am trying to setup rules on a view that will maintain an audit trail
of modifications in the real table. Things seem to be going ok but when
I EXPLAIN my queries, the literal 'now' is being given two different
values, one 2 days earlier. I am running 7.4.7
The view is defined to be;
CREATE
