k Users Mailing List - Non-Commercial Discussion <
> asterisk-users@lists.digium.com>,
> Date: 06/11/2013 08:28 AM
> Subject: Re: [asterisk-users] Is uniqueid/sequence a safe CDR
> table primary key ?
> Sent by:asterisk-users-boun...@lists.digium.com
> ---
To: Asterisk Users Mailing List - Non-Commercial Discussion
,
Date: 06/11/2013 08:28 AM
Subject:Re: [asterisk-users] Is uniqueid/sequence a safe CDR table
primary key ?
Sent by:asterisk-users-boun...@lists.digium.com
Hello,
Still about CDR and MySQL table, should
Hello,
Still about CDR and MySQL table, should the calldate field be inserted by
Asterisk?
This is the table structure we are using, based on Asterisk wiki:
mysql> describe cdr;
+-+---+--+-+-++
| Field | Type
OK, then I'll go with linkedid, uniqueid and sequence number.
Thanks for sharing this on this list
2013/6/3 Matthew Jordan
> On 06/03/2013 11:20 AM, Olivier wrote:
> > Hi,
> >
> > When dealing with CDR SQL tables, I always added an auto-incremented
> > cdr_id key as a primary key, just in case
On 06/03/2013 11:20 AM, Olivier wrote:
> Hi,
>
> When dealing with CDR SQL tables, I always added an auto-incremented
> cdr_id key as a primary key, just in case provided uniqueid key went wrong.
>
> Now I'm facing a situation where I need to insert into a database's
> table and from the dialplan
Hi,
When dealing with CDR SQL tables, I always added an auto-incremented cdr_id
key as a primary key, just in case provided uniqueid key went wrong.
Now I'm facing a situation where I need to insert into a database's table
and from the dialplan, a reference to the CDR record which is currently
pr
