+972 52-548-6969
Small touches: Complex text in RavenDB
time to read 1 min | 162 words
This is what we call a “mini feature”, something that you’ll probably not notice unless pointed out to you. Often, we want to store documents that contain multi line strings properties. JSON has a very simple way to handle that:
And it works, and if the text is small, it is even readable. But it isn’t really working on anything even remotely complex or long. So we have worked to fix that:
Now you can actually read this much more easily. We run into this when we look at stack trace information, where without line breaks, it is nearly impossible to see what is going on.
Comments
This is so simple, but extremly usefull.
I like what I see of RavenDB 3.
This is not a "mini-feature". This is a usability feature. There's a huge difference.
I think I'd rather see it how I stored it with all the newlines and tabs. It can help me identify quickly issues with text, where as this "feature" could make that more difficult. Maybe a toggle between both views would help more.
Khalid, This is a presentation only feature, it only impact how you see things, it doesn't change anything in the way the data is stored.
Does it always do \r\n, or does it support reading/writing just \n too?
Jahmai, We will read \n, but we'll always write \r\n.
I can see @Khalid's point and can see the benefit of a toggle view as well.
+1 for a toggle switch. Sometimes you want to know the exact characters in place...
This probably indicates other problems, but consider a document that contains stringified JSON as one of its properties. i.e. { "requestId": "1234", "requestBody": "{\"foo\":\"bar\",\r\n\"fizz\":\"buzz\"}" } I'm going to get confused! +1 for toggle.
I actually kind of like the way Visual Studio does it in watch windows. Normally you see the encoded text, but you click that little magnifying glass to see it with actual line breaks.
+1 for toggle view
Troy & Koen, There is a toggle for that, sure.
Comment preview