[asterisk-dev] [svn-commits] tilghman: trunkr86065-/trunk/apps/app_meetme.c

[Tilghman Lesher]

On Wednesday 17 October 2007 16:53:27 Dan Austin wrote:
> Tilghman wrote:
> > On Wednesday 17 October 2007 15:32:02 Dan Austin wrote:
> >> Tilghman wrote:
>
> <Snip>
>
> >> The code to make the column names configurable is trivial, and
> >> defaults to setting the column names to the current hard-coded
> >> values.
> >>
> >> I like the flexibility that the configurable column names
> >> offer, but I can and will live with a 'Tough luck, hard-coded
> >> values are the way to go here...'
> >
> > To be clear, my objection isn't so much that customizing the
> > column names is bad, but that it's inconsistent with the rest
> > of realtime.  If you wanted to create a set of patches that let
> > you customize realtime options across the board in some way that
> > wasn't completely loony when you get right down to it (like
> > swapping named columns in the database simply by changing a
> > config file), I could see doing that.  The problem with that is
> > not that it's bad per se, but it's likely to cause a great deal
> > of confusion when somebody looks at a database and assumes that
> > the value "dynamic" in column "host" really means "host=dynamic"
> > when in fact the host field is configured to look at another
> > column entirely.
>
> I had thought I had seen another instance of 're-mapable'
> column names either in the WiKi or similar site, but of course
> I cannot find it now.

cdr_adaptive_odbc has this capability, but of course, that's not a
realtime engine.

-- 
Tilghman