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

[Tilghman Lesher]

On Tuesday 17 May 2005 19:37, Leif Madsen - Certified Asterisk 
Consultant wrote:
> On 5/17/05, Brian West <brian.west at mac.com> wrote:
> > > Ergo, deprecating DBGet represents a loss of functionality.
> >
> > What exactly is lost?  I'm missing it I think.
>
> I think he was just confused as to how the new functionity works -
> there is no loss of functionality, only gains in granularity.

Considering that I wrote portions of the core function code, I'm not
confused.  I've already explained it completely in the previous
message, and I'm not going to repeat myself.

> To get around the supposed loss of functionlity with the n+101
> logic from DBget():
>
> ; * not tested *
> exten => 100,1,Set(blah=${DB(foo/bar)})
> exten => 100,n,GotoIf(${EXISTS(${DB(foo/bar)})}?:novalue)
> exten => 100,n,...
> exten => 100,n(novalue),...

Would you care to actually RUN your code and show me how
EXISTS() differentiates between a non-existent key and a value
which is simply blank, or are you going to continue to bullshit
your way through this exchange?

-- 
Tilghman