Added a much more user friendly way to present the data1-4 labels for each type, now that we have a tender_types table. Still not a perfect solution, but definitely good enough for now. Modified the application to recognize the new tender_types table. There may be other modifications necessary, but this gets the most obvious spot.

git-svn-id: file:///svn-source/pmgr/branches/yafr_20090716@378 97e9348a-65ac-dc4b-aefc-98561f571b83

db/schema.sql

@@ -1131,14 +1131,17 @@ CREATE TABLE `pmgr_tender_types` (
   -- include credit cards, debit cards, and ACH transfers.
   `tillable`             TINYINT(1) UNSIGNED NOT NULL DEFAULT 1,
 
-  -- How many data fields are required/used by this type.
+  -- Names of the 4 data fields (or NULL if not used)
   -- Not the most robust of solutions, especially since
   -- it requires (or strongly implicates) that all fields
   -- be of the same type (ugh).  A more complete solution
   -- would be for each type to have its own table of data
   -- and to have that table specified here.  However, this
   -- is MUCH simpler, and works for now.
-  `data_fields`          SMALLINT UNSIGNED NOT NULL DEFAULT 0,
+  `data1_name`           VARCHAR(80) DEFAULT NULL,
+  `data2_name`           VARCHAR(80) DEFAULT NULL,
+  `data3_name`           VARCHAR(80) DEFAULT NULL,
+  `data4_name`           VARCHAR(80) DEFAULT NULL,
 
   -- When we accept legal tender of this form, where does
   -- it go?  Each type of legal tender can specify an