Closed artem-zinnatullin closed 9 years ago
Just for logging? Do you have other ideas why it may be helpful, listen entire db regardless of the tables?
You can dynamically decide what to filter and yes -> logging, but we will provide logging in some future release…
Logging is essential. Very nice - I'm looking forward.
For now I'm using DBFlow, but storio is getting better and better - and for me it's important that I can use rxjava.
Sure, logging is essential but we'll provide it as separate feature #79.
At the moment user can observe changes of particular tables (in
StorIOSQLite
) or particularUris
(inStorIOContentResolver
).I think it could be useful for users (at least for me and our current work project) to have an API that will allow to observe all changes without filtration, for example for logging and other purposes.
@nikitin-da thoughts? I remember that we discussed this several months ago and decided to provide only
observeChanges(tables)
andobserveChanges(uris)
to prevent users from EventBus-like code, but now I see usages for generalobserveChanges()
API.