[asterisk-bugs] [Asterisk 0011623]: SQL Insert Support For func_odbc

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11623 
====================================================================== 
Reported By:                irroot
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   11623
Category:                   Functions/func_odbc
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.16.2 
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-22-2007 06:47 CST
Last Modified:              12-23-2007 11:28 CST
====================================================================== 
Summary:                    SQL Insert Support For func_odbc
Description: 
here is a patch that i have been using for quite a while and find
invaluable.

1)should the write fail attempt the insert command
2)allow a insert command to set various bits and pieces without
read/write

concider it a small Xmas gift ;)
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 12-23-07 11:28  
---------------------------------------------------------------------- 
I'll note that you can do the same thing by using dialplan code:

n,Set(ODBC_FOO(foo)=123)
n,GotoIf($[${ODBCROWS} >= 0]?done)
n,Set(ODBC_FOOINSERT(foo)=123)
n(done),NoOp

and it's a lot more versatile by allowing the dialplan creator the option
to decide how the failover should happen.

I know there's a lot of push and pull as to how complex we should make the
API, but this is one area that I think we ought to keep on the simple side,
to avoid a great deal of confusion. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
12-23-07 11:28  Corydon76      Note Added: 0075871                          
======================================================================