A while back, a friend told me of a facility that would allow us to "shadow" a production database using a local database. The term shadow may be incorrect (so please correct me if so)
What I understand, and want to do is:
When I make an update / insert, it only impacts the database that is local.
I make a select statement, the return is first the data from the database that is shadowing, then the production data is filled in.
table modifications only impact the database that is shadowing
clear out (roll back transactions?) to get the local to a neutral point.
would prefer not to have to copy the database over, but pull from the live data if possible.
Since this is not designed for production, performance is not really an issue.
The use case in mind is that I would have said database for local / testing, and a quick way to revert all the changes that I had done, if they need to be.