A memory tag that you update just after the data is saved in the database is probably the simplest method. (I would use a datetime memory tag and write system.date.now() to it.) The consumers in the UI would use a tag binding on a session or view or component custom property, with a change event to perform the necessary UI operations to redisplay content (probably a .refreshBinding() method call where the named query resides to make it run again).
The only downside to the memory tag approach is that binding evaluation will likely double-execute the query on view startup.
A more complicated approach that avoids that problem would be to broadcast a message after saving in the database, and having message handlers cause the content redisplay. Take a close look at this topic, and the behavioral differences between system.util.sendMessage() and system.perspective.sendMessage() in regards to gateway scope broadcasts: