Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Talk:EclipseLink/DesignDocs/356812

Revision as of 11:43, 6 September 2011 by Shaun.smith.oracle.com (Talk | contribs) (New page: Shaun: 1. The name of the feature should be generalized to refer to "external" change events rather than "database" change events. Notification may be coming from an external system via,...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Shaun:

1. The name of the feature should be generalized to refer to "external" change events rather than "database" change events. Notification may be coming from an external system via, say JMS, which knows that certain data has been modified (maybe by itself). The database is only one source of external notification.

2. Secondary tables, join tables, etc. can be supported through examination of the descriptors. I have done this myself with secondary table.

3. The Oracle database "DCN" feature has been renamed "QCN": Query Change Notification. I'm not sure in what release of Oracle DB this renaming took place.

4. This feature focuses on invalidation while it may be the case that the updated data for an object(s) is part of the change event. When available, it should be possible to update the cache with the new data rather than invalidate.

Retrieved from "https://wiki.eclipse.org/index.php?title=Talk:EclipseLink/DesignDocs/356812&oldid=267177"

Back to the top