All the fields relating to that user will be removed. The idea with the editing side is to be able to delete an installer from the installer table say with the id of 1 and all other pertinent information in the other tables will also be deleted. Now there wil be one program that deals with the installation side and another that acts as a front end for editing the database suchs as adding new files, removing old files etc. I might separate into two tables, undecided yet.
SQLITESTUDIO FOREIGN KEY CONSTRAINT FAILED INSTALL
Stores the users\computers that are allowed to run the post install actions Postinstall - a list of activities to perform when the main install has finished. Platform - the OS architecture the installer file is compiled for. Package - stores the type of installer, NSIS, Inno Nullsoft etc. Stores the user or computer to install the program for or on.
Installer - this is the main table that has relationships with the other tables and stores info about the installer file, install order etc. I have attached the database thus far and the tables function are as follows:-Ĭategory - stores text describing the general usage the installer comes under, such as Browser, Compression etc. The database is going to store information about setup installers, such as paths, installer specific info, users to install for, type and category of installer blah, blah. I am using SQLite Expert to design the database and test sql queries. I am trying to normalise a database to remove duplicate info.
0 kommentar(er)
