Re: [SR-Users] too long mysql table key

2017-04-15 Thread Juha Heinanen
Daniel-Constantin Mierla writes: > As I said, I haven't added this table, nor use it, my guess was that > this constraint is to avoid having same (did,name,value) more than > once. I have used domain_attrs to store properties that are common to all users of the domain, e.g., which lcr index (=

Re: [SR-Users] too long mysql table key

2017-04-15 Thread Daniel-Constantin Mierla
On 15.04.17 08:30, Juha Heinanen wrote: > Daniel-Constantin Mierla writes: > >> 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 >>

Re: [SR-Users] too long mysql table key

2017-04-15 Thread Daniel-Constantin Mierla
On 15.04.17 08:27, Juha Heinanen wrote: > Daniel-Constantin Mierla writes: > >>> Looks like default charset is something (e.g. utf8), where one char takes >>> more than 1 byte and 767 limit is exceeded. >>> >>> Any suggestions on how to solve this? >>> >> I haven't trying for UNIQUE, but it may be

Re: [SR-Users] too long mysql table key

2017-04-15 Thread Juha Heinanen
Daniel-Constantin Mierla writes: > 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

Re: [SR-Users] too long mysql table key

2017-04-15 Thread Juha Heinanen
Daniel-Constantin Mierla writes: > > Looks like default charset is something (e.g. utf8), where one char takes > > more than 1 byte and 767 limit is exceeded. > > > > Any suggestions on how to solve this? > > > I haven't trying for UNIQUE, but it may be the same as for usual INDEX > where one can

Re: [SR-Users] too long mysql table key

2017-04-15 Thread Daniel-Constantin Mierla
On 14.04.17 17:15, Juha Heinanen wrote: > Juha Heinanen writes: > >> domain-create.sql contains this: >> >> CREATE TABLE `domain_attrs` ( >> `id` INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL, >> `did` VARCHAR(64) NOT NULL, >> `name` VARCHAR(32) NOT NULL, >> `type` INT

Re: [SR-Users] too long mysql table key

2017-04-15 Thread Daniel-Constantin Mierla
Hello, On 14.04.17 17:04, Juha Heinanen wrote: > I tried to install kamailio mysql db on Debian Stretch. Create of > domain_attrs table failed with this kind of error message: > > ERROR 1071 (42000) at line 26: Specified key was too long; max key length is > 767 bytes > > domain-create.sql

[SR-Users] too long mysql table key

2017-04-14 Thread Juha Heinanen
Juha Heinanen writes: > domain-create.sql contains this: > > CREATE TABLE `domain_attrs` ( > `id` INT(10) UNSIGNED AUTO_INCREMENT PRIMARY KEY NOT NULL, > `did` VARCHAR(64) NOT NULL, > `name` VARCHAR(32) NOT NULL, > `type` INT UNSIGNED NOT NULL, > `value` VARCHAR(255) NOT

[SR-Users] too long mysql table key

2017-04-14 Thread Juha Heinanen
I tried to install kamailio mysql db on Debian Stretch. Create of domain_attrs table failed with this kind of error message: ERROR 1071 (42000) at line 26: Specified key was too long; max key length is 767 bytes domain-create.sql contains this: CREATE TABLE `domain_attrs` ( `id` INT(10)