Design improvement to Pricing

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Design improvement to Pricing

In the current database design, the end date for a given price is coded as 0000-00-00 if there is no expiration date.  When doing a date compare this is before all other dates.  Such creates unnecessary complication in all of the routines that attempt to determine pricing.  In effect whenever a price is queried for a given case two queries are programmed.

Changing all expiration dates of 0000-00-00 to 9999-99-99 would eliminate the duplication of queries greatly streamlining the code.

The change is relatively simple.

Can such be considered for a future release of webERP?

Bob Thomas