[asterisk-bugs] [Asterisk 0011887]: [patch] new REALTIME_STORE() and REALTIME_DESTROY() functions

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11887 
====================================================================== 
Reported By:                sergee
Assigned To:                otherwiseguy
====================================================================== 
Project:                    Asterisk
Issue ID:                   11887
Category:                   Functions/func_realtime
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 101373 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-31-2008 06:15 CST
Last Modified:              02-05-2008 13:34 CST
====================================================================== 
Summary:                    [patch] new REALTIME_STORE() and REALTIME_DESTROY()
functions
Description: 
This patch adds new dialplan functions, which utilize store&destroy RT API.


REALTIME_STORE(family,field)=value
creates a new record in the RT storage, and sets field to value specified
on the right.

SET(XXX=${REALTIME_DESTROY(family,field,value)})
acts in the same way as REALTIME(), except that it removes matched record
from RT storage.
====================================================================== 

---------------------------------------------------------------------- 
 otherwiseguy - 02-05-08 13:34  
---------------------------------------------------------------------- 
I went ahead and added the ability to do multiple fields/values (a max of
30).  It is not the most attractive solution, but it does at least add the
functionality until any possible architectural change decisions were made.

Thought I'd go ahead and post it here, get some feedback before
committing. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-05-08 13:34  otherwiseguy   Note Added: 0081714                          
======================================================================