SQLite Mobile Client 4+

For the newbie like I was, sqlite is designed to be serverless; i.e., its databases are in files that the app has direct access to, so its more client-file than client-server. You need only this app and some storage space that Files can access. The UI is a little convoluted but you get used to it. Foreign keys are supported if you use "pragma= foreign_keys on" (since sqlite v 3.6.19) and the proper sqlite syntax described in sqlite docs "Foreign key support" page. The Apple shortcuts actions are the primary attraction here ONCE you understand their syntax ➞ a few working examples would be worth a hundred pages of documentation and hours of trial & error!
I may give it 5 stars for functionality once I figure how to use all the actions.
I would love to see some simple but elegant configurable form styles that could be used on the iphone.

Thank you for your feedback! If you contact the support from the app you could get the help you need.

I am so so very pleased— with the results from, and everyday productivity— that has been facilitated by this wonderfully designed and highly refined application. For years, now, I have loved SQLmobile, and this is an app I will stand beside until the end. As a freelance organ sampleset developer, the world of relational database architecture becomes absolutely critical to go about correctly, and this fully-fledged app hits every point desirable for any query, transactional statement, or workflow tweak you could need. I’ve long since happily migrated my local databases into this app from their former editors and the projects have been a breeze ever since. Absolutely CHOOSE THIS APP!

Thank you for the feedback and thank you for using this app!
It’s well appreciated.

I need to text search 758,411 rows with 7 columns, but unfortunately, the search query runs every keypress, which means it seems promising with a page size of 1000 rows, but with a page size of 1,000,000 rows, the app lags for like 10 seconds every letter you type of your search query. If you could please just wait until the user stops typing to run the query over the page, then it would be a five star app. Also, I think the default of 1000 rows per page makes sense, except when you search for something and find no results, in that case, it could be better to automatically search the next page(s) all the way to the end. Just asking because I have a humongous medical database and need to type a symptom to find all the rows with that symptom easily. Thank you for making this app!

Thanks for the feedback. Please check the new version if it improves search performance.