atomic_redesign
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| atomic_redesign [2022/11/23 15:26] – yetidi | atomic_redesign [2023/03/02 19:41] (current) – [atomic redesign] yetidi | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== atomic redesign ====== | ====== atomic redesign ====== | ||
| + | **note:** change point of view into [[reports update]] | ||
| + | |||
| Right now most calculations going with help of module calc which combine data from different tables into one big structure located in memory. | Right now most calculations going with help of module calc which combine data from different tables into one big structure located in memory. | ||
| Line 43: | Line 45: | ||
| |record_type | |record_type | ||
| |fixed_id | |fixed_id | ||
| + | |||
| + | possible issue here if the film may be running in several formats (tpfs_id). As I see in current FDM this managed by different names of the same cinema, like " | ||
| ===== Box office form ===== | ===== Box office form ===== | ||
| Line 48: | Line 52: | ||
| all days will be locked after whole form clicked as locked | all days will be locked after whole form clicked as locked | ||
| + | |||
| + | we may use new table bo_records, where first_atomic is first day when the sequence is started, and then the flag whether the form is locked or not. | ||
atomic_redesign.1669217178.txt.gz · Last modified: 2022/11/23 15:26 by yetidi