mysql changes - all the mysql related patches from the atomic spec

[jrossi]

This a group of changes related to mysql that have been used in atomic rpm for some time.

@atomicturtle If you have sometime could you detail what this all is for the release notes.

[jrossi]

@ossec as the submitter I can it accept. @atomicturtle uses this in the rpm and we need to get the rpm and src installs to be the same code.

[ddpbsd]

I don't use mysql, or I would test this. If I get some free time I'll try to setup an instance.

[jrossi]

merging this unto master - should pass travis now.

[jrossi]

I would like to get this pulled in before 2.9 so that we can make sure that the code in RPM's match the source release. We should not be calling atomic rpm the same till this happens. <-- going forward ;) i just want to make sure that we release the same code for everything.

Please review @ossec

[atomicturtle]

ossec-hids-mysql-schema-fix1.patch
- removes the index on cat_name

consolidate-alert-mysql-2
- changes dbd to consolidate the alert & data tables into a single table, alert
- adds the alertid field

os_dbd-mysql-replace-query.patch
- drops the select/(insert|update) logic from dbd and replaces it with the faster REPLACE syntax for the signature table

mysql-schema-if-exists.patch
- add IF NOT EXISTS logic to table creation

mysql-schema-is_hidden.patch
- add is_hidden column to alerts table. Used by ASL

mysql-disable-max-id.patch
- drop the arbintrary db_Config->alert_id counter. This mapped to nothing, and caused conflicts with alertid
- update type from smallint to int in schema, and added autoincrement to alert

mysql-schema-tld.patch
- add TLD placeholder to schema (used in ASL)

disable-signature-sql.patch
- disable the signature table generation completely for performance reasons. When enabled this can increase ossec-dbd startup times to well over 10 minutes

[jrossi]

@ossec i can not accept this as i created the Pull Request. Someone else will need to review and accept. I am not worried much as atomic is shipping this now to customers, but we should review it anyway.

[awiddersheim]

I don't know enough about the database stuff to review confidently.

[awiddersheim]

Is @atomicturtle not able to do review and merge this? He seems like the most logical person.

[jrossi]

We are in a weird place - he is also the author. I will move then in soon if someone does not review them soon. Like I said we are shipping this in the RPM's right now.

[awiddersheim]

If you are confident and he is confident than I am confident. Merging.