[asterisk-dev] No unique identifier for CDR

[Atis Lezdins]

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