renlor / saltdatabase Goto Github PK

Database update method currently is not finished.
Check database column names, data types, and default values against yml file.

Allow the user to create a permanent backup from within the application. Allow saving of any backup to an online service as described in #17

Add support for images to be included with each record through yml configuration files

Add a simple backup restore interface which shows a list of all available backups and the dates they were created.

Dynamic list updating as names are typed.

Loading of a newly selected record is slow due to tabs in gui being regenerated every time fix so it updates current interface which will be generated on start instead of every record load by swapping listeners or through a master Record which keeps track of current Record and updates the values through structure navigation.

search box currently does not work fix after #6 to avoid rewriting later.

Create a database backup every 30 minutes of runtime delete oldest backups after 10 or so have built up.

Field, tab, and group names should be stored in a separate table and referenced by an identifier so they can be changed without affecting the columns in the main data table. Per user possibly?

Through a series of auto-generated YML files allow the user to specify default names, values, tabs, data groups, etc.

Add database Sync support so multiple copies of the database can exist on flash drives and sync once plugged into a single computer running the application.

Need a way to keep track of edits since last sync along with date each change was made.

For conflicts where a record has been changed in the master database one or more copies give master database precedence if that setting is selected otherwise allow the user to choose which change set to keep or allow user to merge the changesets.
After #3 , #9

Add a integrated SQL terminal to the application for manual database manipulation.

If yml file does not exist regenerate from the database if the database exists if not copy internal (in the jar) default YML files. After #3

Move Gui generation settings out of .class files into .yml files so it is configurable without recompiling the source.

Add support for importing databases.

Cause unknown memory footprint ~26MB not ridiculous but excessive for what the program does. Not caused by a memory leak so wont be addressed unless it becomes a problem.

Allow in program editing of tab group names on a per user basis probably after #18

Save a minimum of 10 backups any more than 10 are deleted after a week. Add option for an online backup of the database using Google drive, dropbox, or some other online storage service.

Add a logging system to allow finding of user detected problems easier. Include messages on everything the system does using 2 separate dated per entry log files. One file for sql and other for program events/errors.

As long as the user has not changed records store all the changes made by the system such as when the user selects a master check box which auto selects all the items in its group unchecking the box would undo all the automatic changes. Possibly extend this so any change made by the user prior to save can be undone (ctrl-z mabe?)

The record display JList is reloaded for every change. Change so updates only happen to affected elements to increase speed and remove need for the buffer list, "records," from which it is generated.