[asterisk-dev] MYSQL_LOGUNIQUEID conditional

[Chris List Recipient]

I've often wondered the same thing. It must have been omitted by default
to reduce the overhead of creating a GUID. Ha! 

Actually it is not there by default so that you will inevitably forget
to add it back after *every single* update, thus breaking your CDR
processing. Doh!

But seriously, It was probably not there originally and it is the way it
is for backward compatibility to not break all those without a UNIQUEID
column in the database.

-Chris

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Tony
Mountifield
Sent: Friday, March 17, 2006 9:06 AM
To: asterisk-dev at lists.digium.com
Subject: [asterisk-dev] MYSQL_LOGUNIQUEID conditional

Can anyone enlighten me as to why cdr_addon_mysql.c has the conditional
MYSQL_LOGINUNIQUEID, and why the condition is not turned on by default?

I would have thought the Unique ID would always be a useful thing to
log, and can't think why the default is not to.

I guess there's some historical reason from before I got into Asterisk.

Cheers
Tony
--
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev