15 Apr
2017
15 Apr
'17
9:38 a.m.
On 15.04.17 08:30, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
I am fine to drop this unique constraint if nobody else has a reason to
keep it and eventually add some normal indexes that could help when
loading/updating records in database.
Cheers,
Daniel
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
I haven't used this table myself, it's
coming from SER branch, but I
guess the unique constraint is for being sure there are no duplicated
values for the same did/name tuple, but more records with same did and
name.
lookup_domain() adds attributes associated with did to AVPs. Sure there
can be more than one AVP with the same name. Therefore I suggest
removing name and value from the index.