atomic_fdm
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| atomic_fdm [2022/02/05 09:18] – yetidi | atomic_fdm [2022/11/23 08:51] (current) – yetidi | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| each atom has fixed exchange rate for local currency for this cinema | each atom has fixed exchange rate for local currency for this cinema | ||
| - | |||
| - | In feature such record could be modified but as an additional delta for each position only: | ||
| *number of attendance (sold tickets) | *number of attendance (sold tickets) | ||
| *cost of them | *cost of them | ||
| + | *gbo | ||
| + | *nbo | ||
| + | *users_id | ||
| + | *... | ||
| Of course we may also store each ticket. But I think enough to summarize them into ' | Of course we may also store each ticket. But I think enough to summarize them into ' | ||
| - | Each atom store info about the user who did entered | + | The atom should be never modified (or their modification time restricted for example by the day when it was added). Only new atom which refer to this one may be applied in the next dates. |
| - | If the atom require to be modified -- that will be new atom refer to old one as ' | + | That I've describe main processing being with films (box office) |
| - | + | ||
| - | That I've describe main processing being with films. | + | |
| For cost calculation we may also review and write how it should be look as. | For cost calculation we may also review and write how it should be look as. | ||
| + | |||
| + | Also other atomic based things we need to process somehow to have then invoices and payments. | ||
| ===== database rules ===== | ===== database rules ===== | ||
| Line 49: | Line 51: | ||
| When engine will be ready -- we will run all tests to compare old reports with new reports may be even in automic mode which will go through excel reports and compare each cell automatically. | When engine will be ready -- we will run all tests to compare old reports with new reports may be even in automic mode which will go through excel reports and compare each cell automatically. | ||
| + | |||
| + | Then from some day we will go to fdm_2 | ||
| + | |||
| + | **23-nov-2022** keep old UI completely; only change the core; this way help us to keep old working style without of headache about teaching users; | ||
| + | |||
| + | so this way: | ||
| + | *create new database structures and describe each one | ||
| + | *make the conversion scripts which may convert the current database to this style | ||
| + | *arrange new engine on some great place (like third level domain) | ||
| + | *test all report & work to see all is nice | ||
| + | *use new engine for some days | ||
| + | *update old vps for new engine | ||
| + | *move the database from testing place to main website | ||
| + | *continue life with new FDM | ||
| **ok**, this is my draft about how it could be | **ok**, this is my draft about how it could be | ||
atomic_fdm.1644052723.txt.gz · Last modified: 2022/02/05 09:18 by yetidi