Digimer bbf194994e * New attempt to solve the resync issue; Created a new method called Database->refresh_timestamp that will update 'sys::database::timestamp', and call it when UPDATE'ing in '->insert_or_update_jobs()'. This should force the 'modified_date' to be unique per update and allow the existing resync approach to work properly. If so, this method will be used later for any instance where a given record can be updated multiple times per run. ... Signed-off-by: Digimer <digimer@alteeve.ca>		2018-09-25 02:15:44 -04:00
..
Tools	* New attempt to solve the resync issue; Created a new method called Database->refresh_timestamp that will update 'sys::database::timestamp', and call it when UPDATE'ing in '->insert_or_update_jobs()'. This should force the 'modified_date' to be unique per update and allow the existing resync approach to work properly. If so, this method will be used later for any instance where a given record can be updated multiple times per run.	2018-09-25 02:15:44 -04:00
anvil-tools.xml
test.conf
tools.conf	* Updated the database components to use the name 'anvil' and the user 'admin'. The 'database:❌:user' and 'database:❌:name' variables are still supported, but now hidden.	2018-04-13 19:55:34 -04:00
Tools.pm	* Added a row-count check when deciding if a DB resync is needed.	2018-09-22 00:54:37 -04:00
Tools.t	* Changed the Storage->copy() 'target' parameter to 'target_file' to avoid confusion with the often-used 'target' parameter for connecting to remote machines.	2018-04-30 11:43:30 -04:00