Nagios Support Forum

-------- Original Message --------
Subject: Re: [Nagios-devel] Case-insensitive objects in NDOutils
From: Hendrik Baecker
To: [email protected]
Date: 2009-10-22 08:25
>> ALTER TABLE nagios_objects MODIFY name1 varchar(128) COLLATE
>> latin1_bin NOT NULL default '';
>> ALTER TABLE nagios_objects MODIFY name2 varchar(128) COLLATE
>> latin1_bin default NULL;
>>
>> The code then stayed the same. Also it means anything trying to read the
>> data doesn't need to remember to specify BINARY either.

Just to mention - binary casts may slow down selects on large tables.
There were reports in Icinga IDOUtils about that while changing the
collation to case-sensitive will do the trick probably.

Besides there are several queries using SELECT * instead of SELECT
tablename_id generating useless database traffic - two of those are just
for checking if there's an entry or to fetch the object_id.

Another proposal - why not add several indexes from mysql-mods-*.sql
directly into the DB default definition? This would resolve performance
issues on SELECT/DELETE.

The other thing is the duplicated rows stuff. Much to do for NDOUtils
1.5

Kind regards,
Michael

--
DI (FH) Michael Friedrich
[email protected]
Tel: +43 1 4277 14359

Vienna University Computer Center
Universitaetsstrasse 7 A-1010 Vienna, Austria





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]