Fix Pending Status persists for all successful transactions

[GibsonRuitiari]

This PR fixes the pending status that persists after all successful transactions.

Fixes #965 and #961🦕

[jumaallan]

Interesting fix 👏🏽

[GibsonRuitiari]

A little explanation for future persons :-)

When your app components create different instances of a Dao, the instances are not synchronized. Hence you might find that one instance of your Dao is busy updating the database whereas another is busy reading the database. So the one reading the database might in most cases get stale data.

One solution could be providing a singleton instance of your Dao and injecting the instance to all your components. Since you only have one single instance, from how room is designed, it will be up-to-date with the current data in the table.

Another solution could be forcing room to invalidate table instances and subsequently invalidate your Dao instances upon an update so that any component using your Dao will get an updated instance of it. Behind the scenes what room does is it uses a service that tracks the database changes and updates the instances of your Dao's. So anytime your data changes, the instances are updated and the Dao's are always synchronized.

I have gone with the second solution since it is the easier one.

[jumaallan]

A little explanation for future persons :-)

When your app components create different instances of a Dao, the instances are not synchronized. Hence you might find that one instance of your Dao is busy updating the database whereas another is busy reading the database. So the one reading the database might in most cases get stale data.

One solution could be providing a singleton instance of your Dao and injecting the instance to all your components. Since you only have one single instance, from how room is designed, it will be up-to-date with the current data in the table.

Another solution could be forcing room to invalidate table instances and subsequently invalidate your Dao instances upon an update so that any component using your Dao will get an updated instance of it. Behind the scenes what room does is it uses a service that tracks the database changes and updates the instances of your Dao's. So anytime your data changes, the instances are updated and the Dao's are always synchronized.

I have gone with the second solution since it is the easier one.

Thanks for this 👏🏽

[as7r44]

Hello guys,
was this fix merged with main branch or tested and working fine with you ?
As still I am facing this challenge of pending status on successfull transactions