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.
Can you please help to choose from Coredata or sqlite ??
Which one is better ? As I have complex query in database.
This blog will help you a little
http://blog.mcohen.me/2010/06/19/why-i-chose-sqlite-instead-of-core-data/
The answer, of course, is that "it depends". They both have their advantages and disadvantages depending on what you want to achieve.
Check out this article, and others, on choosing between the two: http://answers.oreilly.com/topic/1959-when-to-use-sqlite-instead-of-core-data-on-the-iphone/
Sqlite is a RDMS system and involves SQL and while CoreData is a object-oriented programming within xcode.. Both deal with a lot of data in the database. Both have their own way of writing and saving to the database. You need to know their specific ways... On deciding on which to use, it really depends on the circumstance you are in.. If you are using a simple query or have very little data in the database, you could use plist or userdefaults. The choice is yours because you know best what you need...
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.
I am a Mongo newbie and wanted to know if there are any tools that will help me test MongoDB? Especially, if they help me automate testing of the tables (or collections) in MongoDB. I did a few internet searches but got very confused. Any help will be appreciated.
Thanks!
Two clients I found useful when testing/looking at data within the db are:
MongoVue - It's free and allows you to see up to 3 documents at a time; and has multiple ways of displaying the data (text form, table form, etc.) Quite nifty, but the cool features expire after 14 days, then you have to pay.
MongoExplorer - It's a little less friendly looking thatn MongoVue, but it is very simple to use, and it is absolutely free. It has some more advanced options as well - such as the ability to see GridFS data (this is a paid feature in MongoVue).
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.
My question seems to be dump, but because i was studying this new technique, i've found that NoSql has changed from its beginning, for example, in the beginning there was the problem of see your own update, and for example Facebook dident let users to update their comments due to the write once, read many
So, do i change all concepts that i've read in 2010-2012 tutorials?
Has NoSql beat the CAP theorem ?
I agree this can easily turn into discussion. I'll give brief answers from my experience to your two questions:
No, the concepts haven't changed. The landscape seems to be growing quite a bit as lots of companies get into the NoSQL space. Beware vendor promises!
No way. Just read this article this morning, it is a great explanation on some of the issues with the CAP theorem: http://codahale.com/you-cant-sacrifice-partition-tolerance/
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.
Where ever I read I see experts writing to stay away from typed datasets and use the entity framework or similar.
On the other hand almost every ado.net book I read will show first how to use datasets and some of them only use datasets, that gives me the impression that its not bad. if it is why teach it for the new programers?
All depends on what you want to do with the data you're pulling from your DB.
I use a DataSet to load data in to a Crystal Report because it plays well together. Anywhere else in my app i use mostly anonymous types. Either way i use the EntityFramework to pull the data from my DB. I get results much faster that way than using ADO.NET and DataSets. If i need raw performance I use ADO.NET. For batch updates for example.
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.
We have requirements that force us to have two layers of databases. A good caching solution backed by large distributed database. We are thinking to use redis for fast read and write. We are not yet settled for the database at backend, however we would prefer it to have following properties:
consistent over time.
robust (no data loss).
reasonably fast read.
distributed.
We are exploring cassandra and Mongodb as our options. Hbase might be a option too. Kindly let us know your views/ current state of work. We are expecting some comparative analysis which could be like in http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis , but should be more upto date and can give us better insight. An example usecase could be like when someone post a comment in facebook. The comment is then visible to all its friends in real time.
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.
Is there a good tutorial or something similar for learning how to write Stored Procedures (for a PostgreSQL database). I'm a definite newbie when it comes to writing Stored Procedures at all, so the clearer and simpler things are explained, the better...
Thanks in advance...
You almost had it, but better start here plpgsql
Some will point that PL/pgSQL is not the only way to write Stored Procedures for PostgreSQL and they will be right (that's one of the advantages of Postgres), but on the other hand PL/pgSQL is nice and relatively easy to start with.
Note that obviously, here's a good place to start:sql-createfunction