Question on the local database. I had this database setup early in my project. Everything was working fine with the project. I could save, update and delete data all fine and I could see a reflection of these changes when I opened the database in the browser (testing was done on the browser). Now I added a bunch of columns and things are not so good. I can still save, update and delete but the changes are not shown in the database. Plus, I was able to pull all the data out of the database with some other tools that I wrote fine and now those will not work. Are there any issues with adding columns to a local database later in you project?
Wow this is strange. I do not see the data in the database but other areas of the project that did not work seem ok now? I did clean out the cache completely to remove any local instances of the database thinking that might mess stuff up.
OK, so that being said, how do I completely remove any instance of a local database within the Thunkable testing app?
Hey Gene - I’ve noticed that local DBs seem to be cached – for a really long time lately – at least with Live. I had to clear my cache on my browser to get it to behave. Do a full clear cache (don’t need to wipe passwords but everything else) and it should go back to what’s actually in the designer.
But how do I do that in the mobile app tester?
Uninstall and reinstall thunkable live — at least that’s what’s worked for me
Are you on Android or iOS. If you are on Android, you can go into your app setting in the settings app and clear the cache. If you are on a iOS device, then you will have to follow what @catsarisky recommended. iOS does not have an good way to clear cache.
Thank you. I’m on Android.
Just a note here,
Local DB is stored in the App data section not the cache so clearing cache only would NOT solve the issue. When you uninstall you also clear cache and data and this is the reason why it corrects it.
You meant would NOT solve the issue, right?
Yes you are right. I corrected it.
I have to admit that the issue I was seeing here was two part. The first part was very much about the database structure not updating after I added new columns. The suggestions in this thread helped me resolve that part of my problem.
The other part of the problem was 100% my fault and I should have paid closer attention to my code. I have a function that updated my screen and I had not updated that to reflect the new columns. I take full blame for this and it was not the product at all.
That being said (I’m not trying to dance around that this was my fault) something I have learned about this tool is that, though it is incredibly easy to do most things, you have to build quite the long list of blocks to do any more complex work. This could also have to do with my lack of skills with the product and programing patterns I have learned yet about this tool. But in general, I can get about 70% of the project done but when I need to actually finish it I end up having to jump through hoops.
Is this a fair statement or have others found that after time you have learned the ways of using the tool and been able to get what you want done rather easily?
Thank you for the support!
No worries at all. This happens to all coders specially when something works after number of failed attempts we get high by the success ignoring other bits and pieces that we have to adjust to match the changes.
As for the no-code blocks, yes it needs a different type of thinking and sometimes you think of it as solving a puzzle instead of programming.
Thanks for that info!