This release of Solar includes a minor BC break in how Solar_Sql_Table lets you set up column validation. It also standardizes how validation routines get feedback messages. The change notes are:
\n\n* Solar_Sql_Table\n\n * When specifying a 'valid' key for a column, you now get only\n one validation; if you need more than one validation routine,\n use the 'multiple' method. Also, you can now specify the\n validation message key you want to use, instead of it being\n forced to 'VALID_COLNAME' (where COLNAME is the column name).\n You can still use a string as the 'valid' key value for simple\n validations. These changes per discussion with Jeff Surgeson.\n\n * Uses more Solar_Valid validations internally now\n\n* Solar_Form_Load_Table\n\n * Modified loading logic to use the new Solar_Sql_Table::$_col\n 'valid' key value structure.\n\n* Solar_Valid\n\n * New method feedback() standardizes Solar_Sql_Table and Solar_Form\n calls where a validation message is returned when data validation\n fails; this is the opposite of all other Solar_Valid methods, in\n that an empty return value indicated success, not failure.\n\n * New method range() checks a value against min and max range\n\n * New method rangeLength() checks the length of a value against\n min and max lengths\n\n * Renamed method inScope() to scope()\n\n" }