Re: [Asterisk-Dev] Loss of functionality with depreciation of DBGet/Put?

2005-05-18 Thread Kevin P. Fleming
Brian West wrote: While I'm not trying to argue with you here.. but you can't "database put" from the cli with a value that is empty.. you can with DBPut in the dial plan. You shouldn't be able to dbput if the value is empty. I see no real value in doing so. I think Leif's example was a bit

Re: [Asterisk-Dev] Loss of functionality with depreciation of DBGet/Put?

2005-05-17 Thread Leif Madsen - Certified Asterisk Consultant
On 5/16/05, Kevin P. Fleming <[EMAIL PROTECTED]> wrote: > exten => 100,1,Set(temp=${DB(CFIM/200)}) > exten => 100,n,GotoIF(${temp} = "" ? novalue) > exten => 100,n,... > exten => 100,n(novalue),... I've been trying to figure out the best way of replacing the DBget() n+101 functionality in the IRC

Re: [Asterisk-Dev] Loss of functionality with depreciation of DBGet/Put?

2005-05-17 Thread Brian West
${ISNULL()} ${EXISTS()} function_db_read() will never return NULL. Thats right.. EXISTS and ISNULL are just opposites... NEXT!!! ;) Back atcha. Thanks for the other fix on the bug tracker.. I was about to get around to that. ;) /b ___ Asterisk-Dev m

Re: [Asterisk-Dev] Loss of functionality with depreciation of DBGet/Put?

2005-05-17 Thread Jeffrey C. Ollie
On Tue, 2005-05-17 at 12:27 -0500, Tilghman Lesher wrote: > On Tuesday 17 May 2005 11:02, Brian West wrote: > > > IMHO, as has been proposed before, we need to provide some sort of > > > return code, similar to DIALSTATUS/etc... Then the dialplan can > > > determine the difference between NULL and

Re: [Asterisk-Dev] Loss of functionality with depreciation of DBGet/Put?

2005-05-17 Thread Tilghman Lesher
On Tuesday 17 May 2005 09:22, Russell Bryant wrote: > Chris A. Icide wrote: > > Hey folks, just re-routing a post I caught on users. Seems some > > functionality may have been lost in the internal database function. > > > > > >With the new Set(${DB(CFIM/200)}=300) I get: > > > > > >May 16 12:39

Re: [Asterisk-Dev] Loss of functionality with depreciation of DBGet/Put?

2005-05-17 Thread Tilghman Lesher
On Tuesday 17 May 2005 11:02, Brian West wrote: > > IMHO, as has been proposed before, we need to provide some sort of > > return code, similar to DIALSTATUS/etc... Then the dialplan can > > determine the difference between NULL and "". So, until we can do > > that, > > IMHO, the old functionality

Re: [Asterisk-Dev] Loss of functionality with depreciation of DBGet/Put?

2005-05-17 Thread Brian West
ok this madness works: exten => 566,1,Dial(${IF(${EXISTS(${DB(CF/${CALLERIDNUM})})}?Zap/g1/$ {DB(CF/${CALLERIDNUM})}:SIP/10)}) The parser needs to be more sane with spaces.. but that works. /b On May 17, 2005, at 10:17 AM, Brian West wrote: exten => 100,1,Set(temp=${DB(CFIM/200)}) exten => 100,n,