[asterisk-dev] No unique identifier for CDR

Nick Lewis Nick.Lewis at atltelecom.com
Thu Aug 27 10:09:37 CDT 2009


Atis

I do not have a problem with the name "sequence" or even "seq" but is
this an accurate description in all cases? I do not use ForkCDR but
assume that it will produce cdr instances that unlike ResetCDR(w) are
not linearly related to the call sequence?

Best Regards
Nick

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Atis Lezdins
Sent: 27 August 2009 15:37
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] No unique identifier for CDR

On Thu, Aug 27, 2009 at 5:08 PM, Alexander
Harrowell<alexander.harrowell at stlpartners.com> wrote:
> On Thursday 27 August 2009 14:21:17 Nick Lewis wrote:
>
>> We seem to be in forceful agreement that uniqueid is not unique per
CDR.
>> I like your linkedid+cdrinstance suggestion. Do you think this
>> combination should also be used as the key in sql rather than an
>> auto_increment id?

Actually MySQL works much better if it has one primary key, not
combination, so i will defineately keep id, but of course if You
intend to get reports per-call key on those fields is a must.

Of course implementation is not yet there, but i would like to name
that field short and clear, something like "sequence" or even "seq".

Regards,
Atis

> If you're using SQLite there's the rowid column - a 64 bit unique
identifier
> for each row.

But the problem mentioned above still exists - you can't get that id
before CDR is posted.

Regards,
Atis

-- 
Atis Lezdins,
VoIP Project Manager / Developer,
IQ Labs Inc,
atis at iq-labs.net
Skype: atis.lezdins
Cell Phone: +371 28806004
Cell Phone: +1 800 7300689
Work phone: +1 800 7502835

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2009 - October 13 - 15 Phoenix, Arizona
Register Now: http://www.astricon.net

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

______________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
______________________________________________________________________

_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre.
_____________________________________________________________________
Disclaimer of Liability
ATL Telecom Ltd shall not be held liable for any improper or incorrect use of the  information described and/or contained herein and assumes no responsibility for anyones use  of the information. In no event shall ATL Telecom Ltd be liable for any direct, indirect,  incidental, special, exemplary, or consequential damages (including, but not limited to,  procurement or substitute goods or services; loss of use, data, or profits; or business  interruption) however caused and on any theory of liability, whether in contract, strict  liability, or tort (including negligence or otherwise) arising in any way out of the use of  this system, even if advised of the possibility of such damage.

Registered Office: ATL Telecom Ltd, Fountain Lane, St. Mellons Cardiff, CF3 0FB
Registered in Wales Number 4335781

All goods and services supplied by ATL Telecom Ltd are supplied subject to ATL Telecom Ltd standard terms and conditions, available upon request.



More information about the asterisk-dev mailing list