As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I want to use No-Sql in my application I think RavenDb and MongoDb are good but which one is more integrated with EF?
and is there any documentation for using theme?
Entity framework is built to support relational databases. It has no support for any no-sql or document databases. And when you think about it, it actually doesn't make too much sense, what is the point of using an object relational mapper and producing a relational mapping of a non-relational database?
There are however libraries which support both of these frameworks available for .Net available via nuget. Im sure these would be much more appropriate for your application
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Are there any existing schema template for general web analytics workload, e.g. similar to Google Analytcis, it probably have at least the following tables
users
sites
requests
Since I don't want to re-invent the wheel, I am looking if any existing well defined schema or good relations modeling is suitable for my need.
Any idea?
Remark: I am running on AWS RedShift, but I think most column oriented database should have similar schema.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
MongoDB is not a relational database nor does the product follow a relational architecture. But for someone coming from the world of RDBMS, I would like to know to what extent does MongoDB support ACID (Atomocity, Consistency, Isolation, Durability). Or should we not evaluate MongoDB from an ACID perspective?
How I love documentation: http://docs.mongodb.org/manual/faq/fundamentals/#does-mongodb-support-transactions and this very site: What does MongoDB not being ACID compliant really mean?
There are ways to support transactions in MongoDB and the go driver even has transactional queries inbuilt into it now.
Here is a brief example of a two phase commit: http://cookbook.mongodb.org/patterns/perform-two-phase-commits/ more complex queries would require more work.
Basically the implications of MongoDBs ACID compliance can be explained via the doc pages and that question mostly.
It is probably one of the most talked about subjects in MongoDB and a quick Google search will give you more information than we could in an answer here.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
For select queries, which one do you think will be faster in execution among JPA native query (Hibernate or EclipseLink) or JDBC query?
JPA uses JDBC so both queries will be executed exactly the same way, and have the same execution time.
JPA is an abstraction layer for the DB. It allows you to think less about the DB structure and to think more about the objects you persist.
I am sure that If you are using only native queries from JPA you will get almost the same performance as with plain JDBC, because it is passed directly to the JDBC driver.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I have hacking a little with MongoDB and I want to try to use MongoDB for a whole website. We will give also a try for binary files stocking in MongoDB.
We currently using Ruby on Rails and we also like Django. I know there is already some implementations for this two framework with MongoDB (Mongoid and MongoMapper for Ruby) but in fact I am not reluctant to learn something new. :-)
What do you think is the best web plateform/framework to use MongoDB in production ?
I've been working with and on mongoengine, an "object-document mapper" (like an ORM, but for MongoDB) and Django. It has fairly complete support for MongoDB's data types and CRUD operations, and some nice helpers for aggregation and map-reduce.
(Shameless plug:) You can see my use of some of these features in Nymwit, an online word game I built with mongoengine and Django, and corresponding source code in my github.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I have heard that projects that use EF as their ORM mostly fail when they have huge databases and actually objects that are dealing with several mappings at the same time. Is it true that EF is still not quite ready for big enterprises?
Whoever said that didn't spend too much time working with EF. I've worked on/been involved with several projects using EF with very complex database schemas and large amounts of data and we had no issues outside of your normal problems you encounter with any ORM.