| From: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
|---|---|
| To: | pgsql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: nulls |
| Date: | 2009-03-12 22:39:27 |
| Message-ID: | 8DB8EC84-8624-4231-87F1-7DD781662AFF@themactionfaction.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mar 12, 2009, at 5:50 PM, James B. Byrne wrote:
>
> ...
> and c.date_effective_from >= <transaction_date>
> and c.date_superseded_after <= <transaction_date>
>
> Have I understood things aright?
The one problem I foresee is that changes to the commodity_tax_rates
table may not reflect in transaction dates that have passed. What
happens if a tax is retroactively ended or applied outside these
barriers? Is this tax calculation frozen at the date of the "best
information we have"? If so, you might consider an insert-only table
and linking the tax decision to the row that happened to be in effect
at any time. This would likely require adding a column indicating when
the row was inserted.
Cheers,
M
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2009-03-12 22:45:27 | Re: Question about Privileges |
| Previous Message | Jack W | 2009-03-12 22:32:14 | Question about Privileges |