Link to home
Create AccountLog in
Avatar of David Smithstein
David SmithsteinFlag for United States of America

asked on

Standalone Desktop Database installation options

I want to explore the idea of creating a stand alone version of our main product that can be installed by the end user as a single user system, but I need to figure out how to either make the MySQL installation completely click through, or use another database that would also lend itself to migration to MySQL should the user decide to upgrade to the multi-user client/server system.

There are a handful of trigger tables on the MySQL side that upon the data entry of a parameter, run a list of queries/functions on the database side, that I would need to be able to duplicate if it's not MySQL, and the database needs to be installed with enough initial data to facilitate the new user's login, or I guess I could build a way to capture the initial user information needed to log in with a new user onboarding process after installation.

The client side I already have sorted out, I just need to figure out the back end and we'll be in business.

Right now I'm installing the community version of MySQL, then using Navicat to build out the needed tables and other objects by performing a structure synch with a master database that has all the most current table, view, function, and event definitions.

Any ideas would be greatly appreciated.
Avatar of John Tsioumpris
John Tsioumpris
Flag of Greece image

I guess the natural choice is SQLite or Access.
Avatar of David Smithstein

ASKER

I don't think Access supports using a table event, like upon data insert, to trigger the execution of a set of queries.

Do you know if SQLLite can do that?
ASKER CERTIFIED SOLUTION
Avatar of slightwv (䄆 Netminder)
slightwv (䄆 Netminder)

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
If triggers is what you after SQLite should keep covered : https://www.sqlite.org/lang_createtrigger.html
If it can be done with MySQL, that would be preferable to support the up sale to the bigger installation with minimal extra effort.  Although the linked support text falls a little short of bridging the gap in terms of knowing how to actually set it up.   But this helps me know in what direction to focus next.  Thanks!