I can't delete this table using the interface of NoSQL Workbench after clicking Delete button nothing happened.
ScreenShot
I click on delete but nothing happened I was expecting the table will be deleted
Not sure if this is a table used only for modelling or one that you have created as an actual table. If it's an actual table, ensure you have DeleteTable permissions for the role being used in workbench.
If this is just a modelling table locally, send feedback to the NoSQL Workbench team via the button on the main dashboard.
Related
what changed in appmaker?
Some time ago i could do:
Select a table from the list on the next page and click Import to
create your model. You can import any table that's not a join table.
based on information: https://developers.google.com/appmaker/models/cloudsql#connect_your_app_to_an_existing_custom_google_cloud_sql_database - on Connect your app to an existing custom Google Cloud SQL database
Now this option is not available, only is available:
Create a new table is a SQL database managed by App Maker.
This is not the option i want, i have already all my tables in DB.
The only option i see here is use Calculated SQL or delete all tables from DB and create from the app.
There is any workaround for this and do what i have done until now: using the import option?
Regards
https://developers.google.com/appmaker/release-notes
"With today's release, you no longer can create new Drive Table data models. Your apps can continue to use existing Drive Tables. However, we recommend you upgrade those models to Cloud SQL as soon as possible."
I have an app that includes a datasource created from an existing Cloud SQL table. A column has since been added to the Cloud SQL table (outside of App Maker).
How do I get the App Maker datasource to reflect the new table schema?
You need to go to Settings -> Database and click Check button:
App Maker will show you a dialog with multiple choices. You can opt to import changes from database:
In other words, App Maker supports both Database First and kinda Code First development approaches.
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 deployed the 1st version of my wp8 in wp store and now i want to deploy the update version of it. Though I know the process of update deployment, but my concern is the sqlite file which doesn't get updated.
Here is the scenario, I have sqlite file in the app where user can store config and setting, in new version I added extra tables and I want to these tables should be reflected in the the update without affecting user settings and config.
What points I should consider to take care of this issue?
Thanks!
Assuming the data in the sqlite database is static you can give the database a new name and submit it with the updated app. One first run copy the new database to isolated storage and delete the old version of the database to save space.
If the user is inputting data into the database you will have to include code to modify the database structure on the first run and insert any records into the new table
What do i need to do in order to be able to query across multiple databases which are in the same db engine?
I have added the .edmx file of 1 database, but i only need 1 view from another db.
Thanks in advance!
Here are a couple of options:
Depending on your database platform, make the view from your second database available in your first database. If you're using SQL Server, you can use a linked server. If you're using Oracle, you can use a DB Link. Simply create a view in your main database where the view's select statement utilizes the linked server or db link to reference the view from your second db.
Create a second .edmx file for your second database. This is the route I chose recently. However I was dealing with one SQL Server DB and one was Oracle DB. There were also multiple tables and functions from both being used. I determined that it was cleaner in my case to create two separate data access projects, one for each DB, each with it's own .edmx.
Hope this helps.