I am about to start a flutter project and coming from android kotlin I was looking for the closest database to room.
I have read about floor and hive.
Before spending hours using both to figure out which one to stick to, I was wondering what you suggest guys.
I don't want to use firebase since the data remain mainly on tve user's device.
If you are happy with room and Kotlin I'd say Floor is your best bet for Flutter. While I haven't used either, I have used other object mappers with SQLite as well as Hive.
Now Hive as non-SQL database is totally different from an SQL based database.
Related
For my next flutter project,
Please suggest to me, which will be the best option to implement DB
Moor or ObjectBox
Thanks in advance
It mostly depends on the kind of data you'll be working with. Since the data I'm working with is all relational (stored in Postgres on the back-end) I use Moor. It requires some more setup to join and get the correct data together in the app, but the watch/StreamBuilder capabilities of Moor make it worth it for my use-case. If any data changes in the background, the UI will update accordingly.
If your data exists only within the app or your backend uses a NoSQL solution like Firestore, using NoSQL (Objectbox) to store the objects likely requires much less effort, and is probably preferred. See also this Moor FAQ remark about Firebase.
In the end, as with so many questions in computer science, the answer boils down to "it depends".
Note
I have worked with Flutter + Moor, I do not have experience with ObjectBox. I have worked with Firestore in combination with a React web app before.
I'm a beginner programmer on the dart and flutter. I want to create an app to manage my small shop and save data on a physical device. I searched for any code samples, but I couldn't find anything. Any ideas or suggestions from Flutter professionals to begin my project will be really helpful.
You can either use sharedPrefernce plugin for storing data. But data may be persisted to disk asynchronously, and there is no guarantee that writes will be persisted to disk after returning, so this plugin must not be used for storing critical data.
Another option is Hive fast key-value database written in pure Dart.
you can also explore other options like sqllite or firebase_database
flutter create appname - This can be used to create flutter app
My goal is to create an application on Flutter. My application will integrate a map where users will be visible live on the map (even when they move). I would like to know which database to use?
I am comfortable with SQL but is it possible to integrate in a table the live position of the users?
Should I use a cloud database like FireBase?
And finally, which database will be the cheapest for an application like mine?
Thanks a lot!
If your goal is fast prototyping I would look into "Firebase Realtime Database". It can do what you want. Pricing is a quite subjective matter.
So I know the JDBC Rivers plugin is deprecated so even though it is being used I'd ideally not want to look at using something that is no longer supported.
However I have a few tables in a Postgres database with values that I need to be able to search in a Kibana view. Im new to the ELK stack but i've been messing around with some of their samples to get familiar.
I've seen some mentions of using Stored Procedures/Triggers from Postgres to send to Logstash. Although im not sure if this is the best way. Im not a developer but a QA so my coding skills are "ok" as im used to writing automation tests/etc...
What would be the best way to do this? I would want to probably capture updates to these tables (probably new inserts or updates) OR be able to poll the data every X period of time (30s or something). Lets pretend it's for a weather station and the tables contain humidity data from different weather sensors.
I'd want to be able to search in a Kibana view the Values/Station ID/etc...
Is this doable? Is there maybe a better way than using Triggers/Stored procedures?
I ended up using the JDBC driver and following https://www.elastic.co/blog/logstash-jdbc-input-plugin to get it moving and working (Which it does move). But it was a lot of setup for anyone that may see this answer.
I'm developing a desktop Mac OS X App that saves its very simple data into SQLite with Core Data and a companion mobile App for iPhone that simply needs to read data from the desktop App. Although they share the same Managed Object Model when I load the SQLite database on the mobile app the data takes several seconds to migrate the data. I really would like to avoid this long wait as it appears linearly related to the size of the SQLite file.
Why is data from the same Managed Object Model even needing to migrate at all?
Does anyone know of a way to avoid needing to migrate?
I've discovered what was causing this problem. Although it is probably very obvious I'll relate it so hopefully no one else will make this mistake...
I had two distinct Managed Object Models in my project. Having more than one seems to force Core Data to try migrating to figure out which data matches with which MOM.
As a solution I was able to manually merge the models so both data sources can be represented with the same MOM.