[asterisk-bugs] [Asterisk 0016000]: [patch] Schema problem with res_pgsql

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16000 
====================================================================== 
Reported By:                jamicque
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   16000
Category:                   Resources/res_config_pgsql
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.1.6 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-10-01 06:37 CDT
Last Modified:              2009-10-06 14:34 CDT
====================================================================== 
Summary:                    [patch] Schema problem with res_pgsql
Description: 
When you are using reltime with pgsql, asterisk on every connect check the
table and it's columns. 
For example it's made by querry (for meetme):

SELECT a.attname, t.typname, a.attlen, a.attnotnull, d.adsrc, a.atttypmod
FROM pg_class c, pg_type t, pg_attribute a LEFT OUTER JOIN pg_attrdef d ON
a.atthasdef AND d.adrelid = a.attrelid AND d.adnum = a.attnum WHERE c.oid =
a.attrelid AND a.atttypid = t.oid AND (a.attnum > 0) AND c.relname =
'meetme' ORDER BY c.relname, attnum

The problem is that it does not check the schema. If you have two
different schemas and in every one table meetme, in result Asterisk will
try to insert double statements into one table, which will result in an
error.


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0016001 schema problem
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-06 14:34 svnbot         Status                   ready for review =>
assigned
2009-10-06 14:34 svnbot         Assigned To               => tilghman        
2009-10-06 14:34 svnbot         Status                   assigned => resolved
2009-10-06 14:34 svnbot         Resolution               reopened => fixed   
======================================================================