Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I'm new to Swift and I'm building on a simple app that relies on login/sign up functions for each user. When I wanted to learn about databases in Swift, I came across Core Data and from what I understood it's like cookies/cache that stores data in the user's phone. If that's so, what's the best way to connect the app to a regular database like SQL?
Core Data is an ORM (object-relational mapping) system. Overly simplyfied you build your data model entities and and relationships between them and Core Data cares about the rest. Under the hood it uses an SQLite database by default, but it also can handle other types of storage (e.g. binary or XML).
To answer your question, for Login/Signup purposes you should look into storing user data such as auth tokens etc. in the Keychain.
Related
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 citations by editing this post.
Closed last month.
Improve this question
I am developing an app for keeping attendance records for the students and I am confused about using either SQFlite or Hive for the local database. What are the pros and cons of both? How does each perform in apps with smaller and more complex databases?
I am currently using Hive and it seems like a hassle regarding code readability.
if you want the saved data to be fetched instantly and you won't need complex queries or have relations among the saved entities then go ahead and use Hive since it loads its boxes (saved data) in the memory for instant fetching
otherwise use SQFlite as it's more readable, scalable, and customizable.
in your case and regarding the project you are working on, I believe you should go with SQFlite, maybe in the future you will add some other features not just attendance, and might need to make complex queries.
Both of them work great, but for both proper data modelling is essential.
However, I wonder whether your app can work without storing data externally. In that case, neither is a good option.
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 citations by editing this post.
Closed 6 years ago.
Improve this question
I am working on an enterprise solutions and we are using EF data first for our data access layer. Currently we have around 100 tables in database and we are adding them to one Entity data model. As project will grow we are going to have one big entity data model with around 500 tables.
We are planning to create small modules for each component of application and creating separate entity data model for each.If somebody has experience of this approach then Please share pros and cons of it.
Do you want service layer if not then you can directly create EDMX with 500 tables. Entity Framework will support.
The only issue you will face is - you wont be able to open EDMX file in design mode. You have to deal with it in xml format only.
Also, you need to disable code generation for every time so that project can be load easily.
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 citations by editing this post.
Closed 8 years ago.
Improve this question
I have just started using neo4j to store data in a graph, i.e. friends of friends etc..
But now I need to store standard application configuration data. This isn't graph data really, its settings that the application will use to help it run.
Normally I would store this in a table in a RDMS or in a document in MongoDB.
Can I still store this data in neo4j ? or should I use another database to store it?
Is it beneficial to have 2 databases i.e. neo4j and mongodb ?? Pros and Cons?
Anybody done anything like this?
Thanks in advance
It's perfectly fine to store it in Neo4j, if it is not large binary data.
Then I'd store it in a blob storage and just store references to it.
If you have nested structures you can either decompose them into multiple nodes, use property prefixes or serialize them to a string (e.g. JSON).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I want to make an app like Instagram but the problem is where to store all text and images data, I have used Instagram when there is no connectivity available then app will show the last feeds even when app is freshly openend (not from background). It uses core data or sqlite.
I came across a scaling presentation from instagram a little while back where they talk how they started, using what and then how they approached the challenges.
See the link: http://www.scribd.com/doc/89025069/Mike-Krieger-Instagram-at-the-Airbnb-tech-talk-on-Scaling-Instagram
Hope this helps.
It's not known what Instagram uses. Use whatever you feel most comfortable with. Anything is possible with any storage technology, although some might fit better than others. Also, regarding your question on "core data or sqlite", you can use Core Data with an SQLite database as a backend (way easier than accessing raw SQL). You can also use other backends with Core Data: binary and XML.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
What is the role of SQLLite in iPhone programming? Where do we use it? Is there any nice link to read around this topic in detail with sample code?
SQLite is a lightweight in-memory relational database, that can be used directly by iOS apps, or as a persistent store for Core Data.
Here's a good list of resources about directly using SQLite on iPhone. And the Apple Developer Center has a lot of info on how to use it as a store for Core Data (and how to use Core Data itself, of course).