summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBrian S. O'Neill <bronee@gmail.com>2007-09-17 00:36:11 +0000
committerBrian S. O'Neill <bronee@gmail.com>2007-09-17 00:36:11 +0000
commitb325d4cf52eff1f6630b6e7a9d3b7c41e73b903a (patch)
treedf3975828178ecb439c988acfc0b04fc3a6423c9
parentef4d716bcbd1532dea306e2309b770d8d95e3bbe (diff)
Missing many-to-one join always returns null now.
-rw-r--r--RELEASE-NOTES.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt
index eadcc09..9c6f213 100644
--- a/RELEASE-NOTES.txt
+++ b/RELEASE-NOTES.txt
@@ -35,6 +35,11 @@ Carbonado change history
- Calling Storable.update when there are no dirty properties actually does an
update instead of being "smart" and ignoring the update request. The old
behavior was non-intuitive and interfered with expected trigger behavior.
+- One-to-many join properties which don't exist always return null now, instead
+ of throwing FetchNoneException. Behavior now matches that of nullable join
+ properties, which never threw FetchNoneException. Nullable join properties
+ which resolve to null are cached as before, but non-nullable join properties
+ do not cache null.
1.1 to 1.1.2
-------------------------------