Right now most calculations going with help of module calc which combine data from different tables into one big structure located in memory.

Only this way get us to see “the same” numbers in reports.

But the module eats a lot of memory and cpu having run a lot of small sql queries for each day data.

So the goal of atomic redesign is to keep the film-cinema-day tripples in the database without of care about this module.

This we help us to minimize amount of cpu spent to calculate reports and get the database less confuse.

Ok, now we may review each screen where we edit data about each movie to see how the atomic concept will work so

ok, the concept should help us to avoid next troubles

• fix invoice feature
• modified exchange rates
• good user's logging
• avoid bugs and crazy situations
• get the engine better and stable

contains 7 atomic days; each day can be edited while the form is not locked; note though the days prior day current may be locked for correct everyday dgbos data;

all days will be locked after whole form clicked as locked; the invoices table should have the flag about the records is locked

enough simple: one atomic day when the sale is happened

also simple: one day being added and locked at once

terms applied to all atomic data used anywhere so no changes both in logic and data

Exchange rates applied for the atomic day at the moment when it's entered.

so here we may have a rule: never change old exchange rate; maybe change the table to use exchange rate for every day, not month as today