Document callback const-ness change

1 files changed, 12 insertions, 5 deletions

diff --git a/NEWS b/NEWS
index da2d3ed..8302f3b 100644
--- a/NEWS
+++ b/NEWS
@@ -45,11 +45,6 @@ Version 1.9.0
     namespace. For more information, refer to Section 12.5.1, "pointer" and
     Section 12.5.2, "table" in the ODB manual.
 
-  * New exception, odb::session_required, is thrown when ODB detects that
-    correctly loading a bidirectional object relationship requires a session
-    but one is not used. For more information, refer to Section 6.2,
-    "Bidirectional Relationships" in the ODB manual.
-
   * Session support is now optional and is disabled by default. This is a
     backwards-incompatible change. Session support can be enabled on the
     per object basis or at the namespace level using the new session pragma.
@@ -58,10 +53,22 @@ Version 1.9.0
     where all the objects were session-enabled, simply add --generate-session
     to your ODB compiler command line.
 
+  * The semantics of the callback functions with respect to object const-ness
+    has changed. This is a backwards-incompatible change. Now, the callback
+    function for the *_persist, *_update, and *_erase events is always called
+    on the constant object reference while for the *_load events -- always on
+    the unrestricted reference. For more information, refer to Section 12.1.7,
+    "Callback" in the ODB manual.
+
   * New function, transaction::reset(), allows the reuse of the same
     transaction instance to complete several database transactions. For more
     information, refer to Section 3.4, "Transactions" in the ODB manual.
 
+  * New exception, odb::session_required, is thrown when ODB detects that
+    correctly loading a bidirectional object relationship requires a session
+    but one is not used. For more information, refer to Section 6.2,
+    "Bidirectional Relationships" in the ODB manual.
+
 Version 1.8.0
 
   * Support for the Microsoft SQL Server database. The provided connection