Уровень 0 · материалов: 3
В кластер входят документы, посвященные конкретным техническим проблемам реализации функций в коде и архитектурным подходам к хранению данных.
Общие признаки: технические ошибки в коде, реализация бизнес-логики, архитектура данных
Группа выше: Качество кода против бизнес-целей, ревью и антипаттерны
Смысл: The text explains that standard 1C systems fail to check stock levels when documents are posted retroactively (non-operational mode), and provides a technical code-level fix to enforce these checks for all posting modes to ensure data accuracy.
The author identifies a flaw in 1C systems where retroactive document posting bypasses stock balance checks and provides a simple code modification to fix it.
Смысл: The text explores a conceptual conflict over whether storing the current state of a system (e.g., stock levels) is considered 'denormalization' if that state can be mathematically derived from a historical log of transactions.
A developer asks whether a table tracking current stock levels is denormalization if the totals can be calculated from historical transaction records.
Смысл: The text points to a specific instance of 'bad code' (indicated by the tag 'Говнокод') involving a lock mechanism in a 'Place Order' software function.
A brief reference to a poorly implemented software lock in a 'Place Order' function, categorized as 'bad code'.