I know that in 1C, information registers and accumulation registers are used to store history. What problems did you encounter when using them? What are the pros and cons. I implement the history storage system through the postgresql + 6NF + jdbc bundle, so for comparison, I would like to know how this is done in 1C

    1 answer 1

    In 1C, registers are not only history, they are storage of additional information, returning values ​​by several specified parameters - for example, material, warehouse, period, unit of measure, automatically calculated data at the beginning and end of the period. Or some reference book of values ​​associated with a particular accounting object.

    That is, the history tables may sometimes not be enough, you will need to add related tables. But nothing is impossible - I think, with a competent database architecture, working with history will be no worse than the example of working with the accumulation register in 1C: http://v8.1c.ru/overview/Term_000000176.htm

    When I was working with 1C, I didn’t remember any particular problems, the flexibility of working with registers was stored in memory - you give him the parameters, he gives you ready data.