- 
    Incident report 
- 
    Resolution: Incomplete
- 
    Critical 
- 
    None
- 
    1.9.4 (alpha)
- 
    Mysql server 5.0.67 on Solaris Spac 10 ( SunOS AMM-SUN6-2-1 5.10 Generic_137137-09 sun4u sparc SUNW,SPARC-Enterprise)
As am I preparing my master degree thesis on zabbix, I downloaded zabbix 1.9.4 alpha release of 2.0 for installation and started to do some tests. At the installation I found a bug in the script that is used to create the database for zabbix.
I am working on Solaris Sparc 10 (SunOS AMM-SUN6-2-1 5.10 Generic_137137-09 sun4u sparc SUNW,SPARC-Enterprise), and use mysql 5.0.67 (mysql  Ver 14.12 Distrib 5.0.67, for sun-solaris2.10 (sparc) using  EditLine wrapper ). The bug is found in the database schema file : create/schema/mysql.sql around the line to create the TABLE NAME expression. Mysql server gives error in the line to create the column. I thought that it may be that the name you used for the colum is a key word for mysql itself then it needs to be escaped properly to be accepted as a column name.
create/schema/mysql.sql
The bug for solaris in bold
CREATE TABLE expressions (
expressionid  bigint unsigned   NOT NULL,
regexpid     bigint unsigned    NOT NULL, 
expression   varchar(255)    DEFAULT ''   NOT NULL,
expression_type   integer    DEFAULT '0' NOT NULL,
exp_delimiter   varchar(1)  DEFAULT ''   NOT NULL,   --this is the bug
 case_sensitive   integer  DEFAULT '0'   NOT NULL,
 PRIMARY KEY (expressionid) ) ENGINE=InnoDB;
Here is the fix to that bug for Solaris SPARC 10:
CREATE TABLE expressions (
expressionid  bigint unsigned   NOT NULL,
regexpid     bigint unsigned    NOT NULL,
 expression   varchar(255)    DEFAULT ''   NOT NULL ,
 expression_type   integer    DEFAULT '0' NOT NULL,
 `exp_delimiter` VARCHAR(1) DEFAULT '' NOT NULL,  --this is the fix by escaping the column with  quotes `exp_delimiter`
 case_sensitive   integer  DEFAULT '0'   NOT NULL,
 PRIMARY KEY (expressionid) ) ENGINE=InnoDB;