Is there a way to list all users for a Realm instance from Realm's API? I wanted to list and delete all regular users with a script, since I can't multi select from Realm studio. They have to be deleted 1 by 1.
Related
Basically i want to access two different databases form two different projects in firebase from one flutter app,
For more info ,
I have build a single Flutter app in which ,
some time i want to refer to one database of (Project name "A" ) and some time i need to refer another database of (Project name "B") ,
is there a way to refer to 2 different database at a time in single app.
Thanks in advance.
Yes, it is possible to read data from 2 different Firebase databases through a single app. Simply go to your Home page on your Firebase console and app your app (both iOS and Android, I assume, since you are developing with Flutter) for both databases.
I was just looking for some guidance with my app design. I'm going to have a local sqllite database pre populated with about 1000 records.
These records will need to be read frequently within the app to update the UI.
The records will need to be updated from within the app.
Is a local mysql database the best way to do this or should I be storing all this info in a massive lua table? The database has 2 tables one with 2 columns and one with 10 columns.
I don't want the data to be accessible from outside the app as some of the data is going to be paid for content.
How would I go about releasing updates in the future? If I upgrade my app to version 2 and add new records to the database... how would I go about keeping the users existing data in the database and just adding the updated stuff?
Hope someone can point me in the right direction!
Many Thanks,
Krivvenz.
I think this is fairly simple question. If you need to use data after closing and opening the app you will need sqlite. If the data is created and lost after the app usage, then a table will do. However, the sqlite has also the advantage of querying, deleting and so many other functions without loops etc that you may need to do in tables manually.
You can also append further data during app update. The Sqlite file you create is saved to document directory. That is not deleted if you only update. Simply write a code in your update that reads the existing database and appends the new data. Or create a new file for sqlite and use the old one as backup.
I have an AIR application and I would like use SQLite instead of an XML file to populate the database. I've seen people create the database on the fly and import the data when the application first launches. But also people are using existing databases. What approach do you use to prepopulate the database? Is there a tool to enter basic initial data (~200 records and 2 tables) or should I create the database and contents manually when the app is first installed.
More context
This is a mobile AIR application using Flex 4.6.
There are numerous tools to manage SQLite databases, such as Lita which is an open source AIR application.
If there is no need to revert the database back to its original content, then it could simply be packaged in the app with your populated content.
If restoring the database to its original populated data is required, you could keep a copy of the original database and stage it to the active database in use, thereby replacing the database.
Depending on data and parity of your app to the database model, it wouldn't be unreasonable to populate your database via programmatic implementation in code executed at first launch. There is overhead both in initial launch of your app and perhaps mostly in code you must generate and maintain to create the database.
Typically, I would only follow this pattern if I have a default model with serialization of that model. As in, if I had already built a commit of preferences style data from my models to persist in a database.
We are looking to create a document management area that models a standard folder structure using Azure blob storage in an MVC3 applicaiton.
E.g.
Users can create folders
User can upload documents to folders
Users can list directory contents etc
Users can delete documents
Users can download documents
Now I appreciate Azure Blob storage only has containers and the rest is faked by slashes creating paths. However this sort of functionality seems like the sort of thing someone else must have created?
I did some searching but coultn't find anything. Basically something like CloudXplorer or Azure Storage Explorer but web based
Does anyone know of any azure blob storage implementation with web front end (ideally MVC)?
You can start looking at BlobShare, an MVC application which allows you to upload, download, view, share, ... blobs:
However, for the sorting part you'll need to build something yourself. I would personally consider using the Windows Azure Caching (Preview) to do this; whenever you access a 'directory', cache the blobs in that 'directory' and do the sorting based on the data in teh cache (same applies to paging). And use something like Service Bus Topics / Queues to refresh the cache whenever someone adds/deletes/renames/... a blob (+ timeout for directories not accessed in X minutes).
I also found this sample. http://peterkellner.net/2010/11/12/azure-storage-treeviewer-directory-browser/. It isn't web based but seems to create a basic tree structure and displays it. There is also related discussion here http://social.msdn.microsoft.com/Forums/en-US/windowsazuredata/thread/256cfc0f-bccc-4bf7-b7eb-cb7c7aca0c8a
See my answer over here https://stackoverflow.com/a/65944680/7988162 on how to use the Storage Explorer across all platforms.
Hierarchical blob storage now exists through Data Lake Storage Gen2. Check out documentation here.
I am making a contact book application in Qt.
I want my application to automatically create an QSQLITE database when it first runs and then access this database in future?
Is there a way to do this?
Ya you can create sqlite database at its first run and can make it progressive. Just do it in the constructor of your App and check for the existence of db before cerating it, else don't create. You can access database in subsequent runs of your same App or different App.
Use db.setDatabaseName("databasename.db"); instead of db.setDatabaseName(":memory:");, now your database will be persistent.