We define an internal AccountParty model which defines an unique ID for the
couple account and party based on the first move line created.
Then we define a General Ledger model based on this model.
issue7438
review314091002
Putting empty maturity date on the last term does not reflect properly the
history of the balance. As we consider such line to be paid or received today,
it is better to use the date at which the move was effective.
issue9294
review305481006
We add the flake8 configuration used so we ensure everyone uses the same.
We remove the usage of __all__ for non public API.
When possible, we rationalize the class name according to its __name__ and module.
issue9082
review297061002
The dictionary template2*** must always be filled even if template override is
True because create_*** calls will use this dictionary to not recreate the
records.
issue7938
review54551002
As the diference between end_periods and start_periods is computed, the end
periods should have a value when the start periods is set otherwise and empty
list of periods is used
issue7838
review47721002
We should not use nonexistent period ids in the context and the start_date
must be excluded from the start computation because it is included in the
range (query_get use greater and lesser or equal).
issue7628
review60421002
* Allow callable in copy default
* Support dotted notation in copy default
* Use setdefault in copy
* Copy default when needed
* Do not set default state in copy
* Use callable and dotted notation in copy default
issue5576
issue7648
review72291002
changeset 3de9de3f476c set initial balance value as Decimal. But as the SQLite
Decimal loop break on the first correct instance, it fails to convert other
value coming from the SQL if the default value is tested first.
As there is any way a second loop, it is faster to make the conversion in this
second loop.
issue7284
As there is a check to ensure that fiscalyears does not overlap it does not
make sense to include fiscalyears which end on the same start date as the
start of the current fiscalyear.
issue5131
review41811002
This allow to preserve the full context from balance sheet or income
statement.
Unfortunately both reports are using a different context model so it is not
possible to use a common context model on the account view.
issue6747
review36631002
It is implemented by evaluating the field for all accounts because the
computation can not be reduced into a SQL query as it may require recursive
computation for all previous fiscal year.
It should not be a problem as the number of account is normally quite static
overtime and the number should not exceed the query size of the database
backend.
issue5168
review41521002
This ensures that the singleton is created when setting the account properties.
Singletons models return the default values when no model exists so the saved
multivalues are ignored if the singleton is not created.
issue6421
review36301002