[asterisk-bugs] [Asterisk 0018473]: [patch] Schema selection support

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18473 
====================================================================== 
Reported By:                avf
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18473
Category:                   CDR/cdr_adaptive_odbc
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.0 
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-12-14 11:14 CST
Last Modified:              2010-12-16 04:10 CST
====================================================================== 
Summary:                    [patch] Schema selection support
Description: 
We use CDR with an Oracle backend, via ODBC.  The CDR table exists inside a
schema (called ASTERISKDBA), and there is a synonym (also called CDR) in
the PUBLIC schema.

When cdr_adaptive_odbc.c calls SQLColumns() to get a list of column names,
the result set contains each column twice --- once for the ASTERISKDBA
schema, and once for the PUBLIC schema.  Obviously, this causes INSERTs to
error.

This patch adds a "schema" configuration parameter which, when set, passes
the schema name into SQLColumns().

Setting "schema => ASTERISKDBA" (or, for that matter, "schema => PUBLIC")
fixes this problem in our environment.


<patch deleted from description>
====================================================================== 

---------------------------------------------------------------------- 
 (0129660) avf (reporter) - 2010-12-16 04:10
 https://issues.asterisk.org/view.php?id=18473#c129660 
---------------------------------------------------------------------- 
Ah, yes, you're right.  It assumes PUBLIC, so it works for us because we
have a synonym in PUBLIC, but in general, it does need to be prefixed to
the table name in SQL statements. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-16 04:10 avf            Note Added: 0129660                          
======================================================================