[asterisk-dev] CDR variables

[Tilghman Lesher]

On Sunday 22 November 2009 12:30:03 Olle E. Johansson wrote:
> 22 nov 2009 kl. 19.12 skrev Tilghman Lesher:
> > On Sunday 22 November 2009 08:17:08 Olle E. Johansson wrote:
> >> 22 nov 2009 kl. 15.05 skrev Benny Amorsen:
> >>> "Olle E. Johansson" <oej at edvina.net> writes:
> >>>> Can we make a distinction like channel variables, that system added
> >>>> variables being UPPER CASE in the future? Obviously we all missed this
> >>>> case when we added the CDR availables.
> >>>
> >>> Case distinctions are not so useful if the CDR's are going to be stored
> >>> in SQL. SQL is stuck with case-insensitive column names (often
> >>> ASCII-only). Welcome to 1970.
> >>
> >> Maybe it was more EBCDIC at that time.
> >>
> >> I guess that the proposal at the bottom is better then - to prefix with
> >> underscore.
> >
> > That's fine, I guess.  I probably would need to make that underscore
> > optional in the adaptive drivers, in terms of the column name.  I think
> > I'd rather deal with an 'ast' prefix, much like how many databases
> > reserve 'sys' for their own tables and column names.
>
> The idea with the underscore was to use something stupid internally in
> Asterisk. Maybe each driver could determine how to translate the underscore
> to something else.
>
> I'm fine with "ast-" as a prefix too. Like "ast-rtp-qos-audio"

Given that nothing currently has a dash, and given that the dash character is
not generally a good character in a database column name, I'd prefer if we
eschew the use of any such separator in new CDR column names.  Like
"astrtpqosaudio".

-- 
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com & www.asterisk.org