That sounds like a really good idea!
Of-course, it’s a truly ugly solution… !! I agree!!
But I only need to redefine the installer, not rewrite the entire application. For me, it’s a better choice in this moment.
I’m pretty sure!
Emelie! The installer is for Windows! Excuse me!
The users for Mac and Linux are left alone at this point… (There are no users so no harm is done, trust me!)
This bring up the next thread…
How do you manage different versions in the database!?
Suppose I use SpecialFolder.ApplicationData.myApplication
and at this moment it’s number 8. What when 9 comes!?
Do I open the database and copy the content from 8 to the new in 9…? All the tables and columns?
What if the user skipped from 8 and then install 12 or 13? Then columns will still be missing!
Is there a way to “look inside” a database and see what tables and columns are present and just add the once that are missing!?
I know, this is possible in MS SQL Server. You can send the command “show me all your tables” and a list will appear, "show me all your column names in table [firstTable] ".
So, in MS SQL Server it would be possible to write an editor in a web interface…
All right.
My question is, would this be possible also in SQLite and in Xojo? To open a database and to “speak” with it?
Is it possible to add version history to a database?
I mean, if I use SpecialFolder.ApplicationData.myApplication
and name all databases “database.rsd” (this is not a joke, I do!) I can then assign a version ID to the database itself.
If the version ID is too old, then delete and create a completely new database, if it’s just one step behind, then copy current data into the new database.
Are you with me!?
This is why I would prefer “quick and dirty” because these thoughts (I’ve thought of this before, much, YES!!!) require some serious thinking and will lead to errors…!! :–) Likely, a few, by experience, quite many…!