once again great overview video from you ;) We use triggers for both normal journaling and to send messages to downstream systems (gigaspaces). I enjoyed the Flashback idea, despite control to access Flashback data is a point in time right or any way to get physical sequence ?
Connor McDonald oh you right thats great and seems our lovely oracle :D offers full detail including scn's, xids and even operation type (I for insert, D delete and U update) as I just found learned in: www.oracle-developer.net/display.php?id=320 I haven't used in production Flashback feature, shared it with other colleagues in some desperately times in dev/test environments lol, im going to deep learn more about Flashback it seems. Is there some way to control what tables we would like flashback or not? Or by default all tables are Flashed?
Its 2020 what do recommend now? here is my req- when user submits an action - create completablefuture and return the future to the caller- The completablefture would then create an entry int the database table- the same completablefuture is now will use continous query notification for the result to apper- mean while there is a daemon which is also looking at the continuous query notification which processes the UI entry and places the result. This way the front end and the backend are completely decopuled. Instead of daemon looking for work I also am thinkin to create a database trigger which will call a microservice to execute which will then place the result.
Database change = the data changed. CQN - the results of a query have changed (which allows more granular focus). eg select * from emp where deptno=10 does not change if you delete a row for deptno=20
Excellent overview Connor. Thanks.
you're welcome
Wow, this is awesome
once again great overview video from you ;) We use triggers for both normal journaling and to send messages to downstream systems (gigaspaces). I enjoyed the Flashback idea, despite control to access Flashback data is a point in time right or any way to get physical sequence ?
you should be able to use the "versions between" syntax to get a sequenced list of changes to the table
Connor McDonald oh you right thats great and seems our lovely oracle :D offers full detail including scn's, xids and even operation type (I for insert, D delete and U update) as I just found learned in:
www.oracle-developer.net/display.php?id=320
I haven't used in production Flashback feature, shared it with other colleagues in some desperately times in dev/test environments lol, im going to deep learn more about Flashback it seems.
Is there some way to control what tables we would like flashback or not? Or by default all tables are Flashed?
Its 2020 what do recommend now?
here is my req- when user submits an action - create completablefuture and return the future to the caller- The completablefture would then create an entry int the database table- the same completablefuture is now will use continous query notification for the result to apper- mean while there is a daemon which is also looking at the continuous query notification which processes the UI entry and places the result. This way the front end and the backend are completely decopuled. Instead of daemon looking for work I also am thinkin to create a database trigger which will call a microservice to execute which will then place the result.
Not really sure what you're asking here. Maybe pop a question on asktom.oracle.com
CQN is.... Similar to DCN.
What is the difference from DCN (database change notification)?
Database change = the data changed.
CQN - the results of a query have changed (which allows more granular focus).
eg select * from emp where deptno=10
does not change if you delete a row for deptno=20
I think kafka is best option