I like how cleanly an object is stored in ravenDB, but have a practical question for which I\'m not sure of the best answer.
Closed. This question is opinion-based. It is not currently accepting answers. Want 开发者_高级运维to improve this question? Update the question so it can be answered with facts and citati
It seems like I run into lots of situations where the appropriate way to build my data is to split it into two documents.Let\'s say it was for a chain of stores and you were saving which stores each c
I am developing a web-based application using Rails.I am debating between using a Graph Database, such as InfoGrid, or a Document Database, such as MongoDB.
I\'ve been looking at the rise of the NoSql movement and the accompanying rise in popularity of document databases like mongodb, ravendb, and others.While there are quite a few things about these that
Here is a document in the store: { \"Name\": \"Hibernating Rhinos\", \"Employees\": [ { \"Name\": \"Ayende\" },
I\'m planning to write an address book that stored contact information. Each contact could have an unlimited number of fields.
For a new project I\'m working I have the need to store some data into a database. The type of data and access model fits well with the NoSQL model and document databases. We are considering things li
I\'m trying migrating an existing web application to use RavenDB. I currently have pages in my web application which allow you to view Categories, SubCategories and Resources based on an id in the qu
I\'m currently configuring my schema.xml file and trying to figure out what\'s the best way to set up my documents. I use a RMDBS and thus many objects are relational.
加载中,请稍侯......