[asterisk-bugs] [JIRA] (ASTERISK-25628) res_config_pgsql: Incorrect behavior when column does not exist
Joshua Colp (JIRA)
noreply at issues.asterisk.org
Mon Dec 28 10:20:33 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-25628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Colp updated ASTERISK-25628:
-----------------------------------
Assignee: Dmitry (was: Unassigned)
Status: Waiting for Feedback (was: Triage)
When the requirements option is set to "warn" the Postgresql driver outputs a warning and does nothing else. This is what this value is supposed to do. If something subsequently uses the table and expects a column to exist that doesn't then it won't work. If you use the "createclose" or "createchar" values then it will attempt to alter the table to add the column.
What are you expecting to happen in this situation instead?
> res_config_pgsql: Incorrect behavior when column does not exist
> ---------------------------------------------------------------
>
> Key: ASTERISK-25628
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25628
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_config_pgsql
> Affects Versions: 13.6.0
> Reporter: Dmitry
> Assignee: Dmitry
> Severity: Minor
> Attachments: patch.txt
>
>
> When column not exist in database require_pgsql() return 0
> and other code does not work properly (for example in main/logger.c logger_queue_rt_start()).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list