+972 52-548-6969
RavenDBSafe by default design – it works!
time to read 1 min | 80 words
Originally posted at 4/4/2011
One of the things that I really tried to do with RavenDB is to make sure that it is safe by default, which means that it will automatically detect common errors and warn you about it.
Today I run into the following Stack Overflow question.
What can I say, it works!
More posts in "RavenDB" series:
- (02 Apr 2025) .NET Aspire integration
- (25 Feb 2022) Domain Modeling and Data Persistency
- (07 Feb 2022) Practical Considerations for ACID/MVCC Storage Engines
- (21 Nov 2013) The Road to Release
- (26 Mar 2012) Self optimizing Ids
- (27 Feb 2012) It was the weekend before the wedding…
- (17 Feb 2012) Index Boosting
- (12 Sep 2011) Multi Maps / Reduce indexes
- (24 Apr 2011) Let us write our own JSON Parser, NOT
- (17 Apr 2011) Safe by default design – it works!
- (29 Sep 2010) Splitting entities across several documents
- (22 Sep 2010) Replicating to a relational database
- (12 Aug 2010) Includes
Comments
It's a good default, but it's also classic example of safe by default is not understood by default.
Perhaps the warning could include a link to a page explaining what's going on and why.
Bravo! A link is what's needed for those mortals among for us with Simple Minds who can write bullet-proof software without the need (or desire) of propeller caps.
If only all libraries and frameworks threw error messages like this.
So much better than "An exception of type System.Exception was thrown". I'm looking at you TFS. Total F'in Sh*t.
Comment preview