Hello CMDBuild Team!
We use openMAINT latest version.
We already use REST web service to "POST" a record or "PUT" to update if the record already exists.
Specifically, we have a mysql database from which we retrieve data to POST/PUT to openMAINT, in a daily basis.
In every POST/PUT all the data of the record are sent as an array, without checking if and which specific attributes have changed, in order to save some REST transactions.
The problem is that by this way the History tab becomes full of updates (daily update) even if no change in the record has occurred (in the case already existing records).
Could you please suggest me a way to insert/update records from a database to openMAINT, where the History would show only real changes?
Thank you a lot!
Regards,
Dimitris
We use the Advanced Connector framework that we have developed, which first analyzes the two sets of data and then performs only the operations (insert, update, status change) required to synchronize them.
CMDBuild Team
Hello again CMDBuild Team,
regarding the History tab again, I would like to manually delete some rows from the postgresql database.
Approaching this issue with caution,
should I delete the desired rows only in the "XXXXX_history" table of the database or should I also delete these rows in the "XXXXX" table?
I am asking because I observed that the old records are kept in both tables XXXXX and XXXXX_history. Why is that, by the way?
Thank you,
Dimitris
The history cards are physically stored only in the history tables.
If you do a “select * from ONLY tablename” you can verify this.
Be careful because if you manually delete rows from history tables and you don’t delete them from the relations history tables, the database will become inconsistent.
In general we recommend these activities only for advanced users.
CMDBuild Team