Hi there,
The issue MR-ISSUE-536 was just created by Gareth Farrington ([email protected]).
Key: MR-ISSUE-536
Summary: ARDataBind Treats the Empty Guid as Null
Type: Bug
Importance: Blocker
Description:
Currently the ARDataBinder and the ARFetch attribute have inconsistent
behavior.
It is possible to ARFetch against the empty Guid (Guid.Empty). It is not
possible to use the ARDataBinder to lookup against the empty Guid. The
ARDataBinder has a method which checks keys and it equates the empty Guid (and
the number 0) as if the input were the empty string or null.
This is a blocker for us because we have entities that use the empty Guid as a
key. We can currently fetch these using ARFetch but we cant bind them using
ARDataBind. So in some cases we cant use the ARDataBinder where we want to.
I have a patch that would add a switch to the ARDataBind attribute so you have
set "TreatEmptyGuidAsNull = false". The attribute is set to true by default so
the current behavior wont change.
Personally I would like to see the behavior of ARFetch, ARDataBind and Databind
be more consistent. That would be a breaking change for some users so the patch
I am submitting does things in a way that will not break current application.
If the maintainers what to address this in a way that makes the API consistent
then I would be happy to write a patch for that too.
For more, see
http://support.castleproject.org/projects/MR/issues/view/MR-ISSUE-536
--
donjon
by Castle Stronghold
http://www.castle-donjon.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
