[asterisk-bugs] [Asterisk 0011040]: [patch] Add user/admin menu options to extend a RealTime scheduled conference
noreply at bugs.digium.com
noreply at bugs.digium.com
Fri Mar 21 19:34:27 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11040
======================================================================
Reported By: DEA
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11040
Category: Applications/NewFeature
Reproducibility: always
Severity: feature
Priority: normal
Status: feedback
Asterisk Version: 1.6.0-beta4
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 86150
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 10-19-2007 13:17 CDT
Last Modified: 03-21-2008 19:34 CDT
======================================================================
Summary: [patch] Add user/admin menu options to extend a
RealTime scheduled conference
Description:
This patch adds *5 to both user and admin menu options
in app_meetme, which will update the RealTime database with
a new conference endtime by a configurable period of time
if it does not conflict with another scheduled conference.
======================================================================
----------------------------------------------------------------------
DEA - 03-21-08 19:34
----------------------------------------------------------------------
I am struggling to get Postges usable on my development system,
so that I might be able to address the concerns.
I have failed miserably to get res_odbc and Postgres to play nice
together,
but I have been able to confirm that Postgres does not puke on this:
psql# SELECT * FROM booking WHERE starttime<='2008-03-21 15:21:00' AND
endtime>='2008-03-21 16:21:00';
If the record exists, it is return, and if nothing is between those
times,
zero records are returned.
I found a logic flaw with how I initially handled checking for early
callers
(already merged), and I'd like to submit the patch to fix it, but I
suspect
the same concerns will be raised.
If the issue is not the WHERE clause, let me know what I should be
testing.
Issue History
Date Modified Username Field Change
======================================================================
03-21-08 19:34 DEA Note Added: 0084416
======================================================================
More information about the asterisk-bugs
mailing list