Pedro M. Baeza

What more to debug/verify that is not in that view?

I would like to know the goals that motivate this refactoring to judge about the huge changes.

But I don't see such a problem, as if you have the last identifier, you use it, and if not, you put the interval. I'm using this module already 2...

I have also the pulling each hour:  I can't accept this huge refactoring that also means to store a lot of useless transactional information unless a good reason for...

There's no scheduling in journals... Debug information should be put on logs and when requested, not stored on DB IMO.

OK, on the provider... It's also hourly: 

The eventual errors that happen with Ponto is due to communication problems, so storing what can be communicated twice (on the statement lines and this new model) is redundant.

Adding such buffer only complicates things and can provoke awkward situations like relying on local buffer while it's not complicated, among the unneeded increase of space, so I'm against such...

As said, it complicates the data model and put more things in the middle to fail. Please don't add the intermediate buffer.

The fact that they pushed that on an old branch that I didn't monitor doesn't make this as something mandatory to be merged now on this branch, and more having...