[asterisk-bugs] [Asterisk 0017872]: update_odbc always reports that : Key field 'ipaddr' does not exist in table ... Update will fail

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17872 
====================================================================== 
Reported By:                spanov
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   17872
Category:                   Resources/res_config_odbc
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.2.11 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-08-16 15:04 CDT
Last Modified:              2010-08-16 18:55 CDT
====================================================================== 
Summary:                    update_odbc always reports that : Key field 'ipaddr'
does not exist in table ...  Update will fail
Description: 
I've set up reatime configuration for sippeers and sipregs via ODBC
connected to Oracle 11g. There are a lot of warning (update_odbc always
reports that : Key field 'ipaddr' does not exist in table ...  Update will
fail) in the CLI while new SIP registration.
I assume that it's case sensitive issue since actually, the column ipaddr
is updated correctly. By default Oracle return all columns in uppercase.
====================================================================== 

---------------------------------------------------------------------- 
 (0126003) tilghman (administrator) - 2010-08-16 18:55
 https://issues.asterisk.org/view.php?id=17872#c126003 
---------------------------------------------------------------------- 
Your assumption is incorrect, because the column comparison is already done
in case-insensitive mode.  Perhaps your Oracle driver does not trim spaces
from column names when returning results from SQLColumns()?  That would be
one way that this could fail. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-16 18:55 tilghman       Note Added: 0126003                          
======================================================================