I'm trying to find a way to localize entity properties in NHibernate that
fits an existing schema.
I've been through the forums / stackoverflow etc so not trying to start a
debate on localization
I've got very close to something I'm happy with. I end up with a fluent
mapping that looks like
HasMany(p =>
p.LocalisedValues).KeyColumn("AKeyColumn").ApplyFilter<LocaleFilter>("LocaleId
= :localeId").Cache.Region("Test").ReadOnly();
where LocalisedValues is a collection of object that has a property for
each property of the entity I want to localize.
I can set the filter immediately after creation of the session and it all
works very nicely until I look at the caching.
Looking through the debug logs I get "Refusing to add to cache due to
enabled filters" and looking at the source I can see why that is.
My questions are
1. Are filters the only way I can reduce the LocalisedValues collection to
just the values for the current locale?
2. I see that the message about caching comes directly from hibernate. If I
wanted to have a go at implementing caching for filters what process should
I follow?
Is nHibernate just a straight port of hibernate or do its features diverge?
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/nhusers/-/POJPddNjbNEJ.
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/nhusers?hl=en.
