Enhanced Billing Timestamp Support
Bug #1748924 reported by
Dan Wells
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
As discussed at Hack-a-way 2016, rather than continue to try to cram multiple meanings into one timestamp, let's create a complete set of all the useful timestamps for a typical billing.
In this new config, every billing will have a 'create_date', then most (overdues) will also describe when they start and end.
billing_ts is now deprecated, but will continue to exist for backwards compatibility. It will be managed by trigger to approximate its current definition; equal to 'period_end' for overdues, equal to 'create_date' for other billings.
Changed in evergreen: | |
assignee: | nobody → Jeff Godin (jgodin) |
Changed in evergreen: | |
assignee: | Jeff Godin (jgodin) → nobody |
Changed in evergreen: | |
assignee: | nobody → Jeff Godin (jgodin) |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Branch for consideration at: git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ dbwells/ lp1748924_ redo_billing_ timestamps
http://
working/ dbwells/ lp1748924_ redo_billing_ timestamps
This is a major rethink of some billing timestamp work done locally a few years back (see LP#1422379), and now that it is done, I think we may still end up reimplementing a COALESCE( period_ start, create_date) single value in the long run, but we'll see how that plays out.
This branch attempts to make the minimum changes to allow for this DB enhancement. Should this be accepted, I have several other bug fixes which build on the availability of these new values.