Portfolio Performance database – ppxml2db import/export

[flywire]

None of my securities are read without omissions. It is difficult to identify parts of the original PP data file that are dropped when running it through ppxml2db and db2ppxml.

issue 18 comment:

So, bottom line: with 1.7.1, if you

1. take your original Testfile_Selfwealth.xml (from the attached zip archive),
2. round-trip it through ppxml2db.py/db2ppxml.py,
3. then open in the latest version of PP, then save, you get “canonical” XML,
4. and if you try to round-trip it again, there’re no further changes

That’s the intended behaviour

While this is not not described in the README.md the process makes it nearly impossible to trace omissions and changes to the original data, especially with real user files because no trace is left of attributes stripped from every security. The development is also linux focused so things like newline characters in notes can be corrupted for Windows users.

@flywire

ppxml2db can most likely import your data into a db but it can’t be relied on for updates until it can rewrite the original xml file without omissions. If it can do that it is fantastic but for many there will be unsupported features.

pfalcon writes:

[ppxml2db] potentially opens a possibility to integrate database backend directly into PP (by making at least a first step - providing a realisitic database schema for that).