asterisk users - Aug 2007 - REALTIME application vs RealTime function

Thanks.

In app_realtime, it is very easy to get a value of a field by only
applying the realtime application.  However, in func_realtime, we need
to get the key-value pair according to the position of it by using
function CUT.  After that, we need to apply another CUT to get the
value.  It will cause the following problems.
http://www.voip-info.org/wiki/index.php?page=Asterisk+func+realtime

1. Changing table scheme will affect the position of the key-value
pair.  That's mean we will can the wrong key-value pair.
2. If the value of a field is NULL, the position will be shifted.
That's mean we need to handle the NULL value using more logic.

In the case, I just wonder why we need to give up the app_realtime.
Or we have another alternative to get a value easily and faster using
func_realtime.  Anyone using func_realtime can give me some advices?

On 8/13/07, James FitzGibbon <james.fitzgibbon at gmail.com>
wrote:
> On 8/13/07, Rilawich Ango <maillisting at gmail.com> wrote:
> > However, I found the the function will be depreciated in 1.4.  There
> > is a replacement using application REALTIME.  I found that it is very
> > troublesome to use it.
>
> I'm afraid I don't have any advice with regard to your problem, but
you
> might want to note that you've got the terms backward.
>
> The deprecated application you're using is app_realtime.  The suggested
> migration is to func_realtime.
>
> * The REALTIME() function is now available in version 1.4 and app_realtime
> has
>   been deprecated in favor of the new function. app_realtime will be
removed
>   completely with the version 1.6 release so please take the time between
>   releases to make any necessary changes
>
> --
> j.