From: | Andy Chambers <achambers(dot)home(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Testing Views |
Date: | 2015-05-20 07:47:48 |
Message-ID: | CAHnaAczEU5hFGTw1EmsCK4yrwXqTqsVO32EqZXWDh5x+TedR+A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello All,
I have a problem for which a view seems like a nice solution. Basically we
want to see all records in some table that are older than 5 days and
haven't yet gone through further processing.
This particular view is probably simple enough that it doesn't require unit
tests but I wonder how people test complex views that depend on the current
date or time. I found a thread on the hackers list [1] that talked about
stubbing pg_catalog.now() but was wondering if any TDD minded developers
had invented anything better since then.
One option I thought of was to just not use views that depend on the
current date or time and instead create a set returning function that takes
the time as a parameter. Would such a function have similar performance
characteristics to an equivalent view?
Cheers,
Andy
[1]:
http://postgresql.nabble.com/overriding-current-timestamp-td5507701.html
From | Date | Subject | |
---|---|---|---|
Next Message | Sameer Thakur | 2015-05-20 08:03:16 | Re: Optimizing a read-only database |
Previous Message | Sachin Srivastava | 2015-05-20 07:25:00 | Memory Utilization Issue |