[asterisk-bugs] [Asterisk 0012745]: [branch] RT should adapt to existing columns on updates

[noreply at bugs.digium.com]

The following issue is now READY FOR TESTING. 
====================================================================== 
http://bugs.digium.com/view.php?id=12745 
====================================================================== 
Reported By:                Corydon76
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12745
Category:                   Resources/NewFeature
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-28-2008 16:13 CDT
Last Modified:              05-28-2008 16:14 CDT
====================================================================== 
Summary:                    [branch] RT should adapt to existing columns on
updates
Description: 
http://svn.digium.com/svn/asterisk/team/tilghman/adaptive_realtime/

This branch does a number of things that will make adding new columns that
get updated by the database less trouble.

1. It registers columns that get keyed off of and updated from a module
through the realtime interface.  The RT engine then looks at the table
layout and ensures that each column exists and is of the proper type to
receive the data necessary.  If the column does not exist, then the engine
may either warn the user or, optionally, create the column automatically.

2. At update time, if a column to be updated does not exist, then the RT
engine will drop the column from the query, rather than what it does
currently, which is to execute a query with unknown columns, which causes
the entire update to fail.

3. Certain modules, such as voicemail, can check, for example, if a
password column is long enough to receive a password and warn the user if a
password truncation might otherwise result.  This should help
administrators a great deal in the future.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-28-08 16:14  Corydon76      Severity                 minor => feature    
05-28-08 16:14  Corydon76      Status                   new => ready for testing
======================================================================