Dynamic Price Updater

[Design75]

Recommend (if not already considered) also that the DB_PREFIX."configuration be changed to simply TABLE_CONFIGURATION as in the below and the configuration_id be removed so that it is system independent and because it is auto_generated (some systems don't like NULL and require 0, but they both end up doing the same thing, assigning the next id.. Update is shown below, another recommendation is a matter of "taste", but one may assume that the addition of a key is not the same as a modification of it (also see the example sql for populating the database with the demo product that the last_modified field is generally not set to a date), so the last_modified field probably could be left off the insert. That has not been incorporated below):

$sql = "INSERT INTO ".TABLE_CONFIGURATION." (configuration_title, configuration_key, configuration_value, configuration_description, configuration_group_id, sort_order, last_modified, date_added, use_function, set_function) VALUES ('Dynamic Price Updater Status', 'DPU_STATUS', 'false', 'Enable Dynamic Price Updater?', '".$dpu_configuration_id."', 10, NOW(), NOW(), NULL, 'zen_cfg_select_option(array(''true'', ''false''),')";

THanks, this is somethying i already had changed in the test version. Theoretically it is possible someone changes the name of the configuration table.