How come properties with only a getter are serialized to RavenDB?

[Dos]

I have a couple of properties that are calculated based on the values
of other properties. These are getter-only properties. How come
they're being persisted to Raven? I can see the values of these
properties in Raven Studio. This seems strange, since there's no way
Raven could deserialize those values back in to the object?

[Kijana Woodard]

You'd think so, until you saw this:

https://github.com/ayende/RaccoonBlog/blob/master/RaccoonBlog.Web/Models/User.cs 

Check out  HashedPassword and passwordSalt.

I tried this...and it just works.

[Dos]

Well, there's a private set on HashedPassword. The property I'm
talking about literally had no setter, and is calculated from other
values on the object, so even if Raven could somehow magically set the
computed getter-only property, I wouldn't want it to. So what gives??

On Jun 2, 6:15 pm, Kijana Woodard <kijana.wood...@gmail.com> wrote:
> You'd think so, until you saw this:https://github.com/ayende/RaccoonBlog/blob/master/RaccoonBlog.Web/Mod...

[Itamar Syn-Hershko]

They will be persisted, but will not deserialize. If you don't want it serialized put a JsonIgnore attribute on it.

[Oren Eini (Ayende Rahien)]

Dos,

It is a useful way to expose calculated properties for indexing / projection.

[Dos]

That makes perfect sense!  Thanks very much to all of you for your replies.  I'll use the [JsonIgnore] attribute for now on those properties I don't want serialized, and keep that in my back pocket for any projections/indexing.

Thanks!

On Sunday, June 3, 2012 2:18:26 AM UTC-5, Oren Eini wrote:

Dos,

It is a useful way to expose calculated properties for indexing / projection.