Apreciado Nagios-devel-request,
Con fecha viernes, 30 de octubre de 2009, 23:28:11, escribi=F3:
ndrlsn> Send Nagios-devel mailing list submissions to
ndrlsn> [email protected]
ndrlsn> To subscribe or unsubscribe via the World Wide Web, visit
ndrlsn> https://lists.sourceforge.net/lists/lis ... gios-devel
ndrlsn> or, via email, send a message with subject or body 'help' to
ndrlsn> [email protected]
ndrlsn> You can reach the person managing the list at
ndrlsn> [email protected]
ndrlsn> When replying, please edit your Subject line so it is more specif=
ic
ndrlsn> than "Re: Contents of Nagios-devel digest..."
ndrlsn> Today's Topics:
ndrlsn> 1. Re: Case-insensitive objects in NDOutils (Ton Voon)
ndrlsn> 2. Accessing host_list/service_list within NEB module (Mathieu=
Gagn?)
ndrlsn> 3. Re: Accessing host_list/service_list within NEB module
ndrlsn> (Ricardo Maraschini)
ndrlsn> 4. Re: Case-insensitive objects in NDOutils (Hendrik Baecker)
ndrlsn> 5. Anyone know why disabled hosts and services are counted w=
hen
ndrlsn> calculating host and service latency from nagiostats and
ndrlsn> extinfo.cgi? (Max)
ndrlsn> 6. Patch RFC - Nagios 3.2 - permanently remove sleep on
ndrlsn> run_event =3D=3D FALSE in main loop (events.c) or condition=
ally
ndrlsn> remove using nagios.cfg configuration parameter? (Max)
ndrlsn> 7. [PATCH] Fix event broker callback functions self
ndrlsn> de-registering for callbacks (Sean Millichamp)
ndrlsn> -----------------------------------------------------------------=
-----
ndrlsn> Message: 1
ndrlsn> Date: Thu, 22 Oct 2009 11:09:44 +0100
ndrlsn> From: Ton Voon
ndrlsn> Subject: Re: [Nagios-devel] Case-insensitive objects in NDOutils
ndrlsn> To: Nagios Developers List
ndrlsn> Message-ID:
ndrlsn> Content-Type: text/plain; charset=3D"us-ascii"
ndrlsn> On 22 Oct 2009, at 07:25, Hendrik Baecker wrote:
>> Am 22.10.09 05:33, schrieb Ton Voon:
>>> Quick note. I saw this change below and wondered if this is best =20
>>> done in
>>> the database. For Opsview, we made this change about 2 years ago =20
>>> for the
>>> same effect:
>>>
>>> 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 =20
>>> read the
>>> data doesn't need to remember to specify BINARY either.
>>>
>> Yes it looks nicer and will keep the code cleaner. Also I like the =20
>> fact
>> to keep the work on the database.
>> One question back: If it uses COLLATE latin1_bin, the default sort =20
>> thing
>> would be binary which is OK but afaik there are other associations =20
>> with
>> the charset
>> (http://dev.mysql.com/doc/refman/5.1/en/ ... lation-=20
>> charset.html).
>>
>> What will happen on a simplified chinese as default charset mysql if
>> ndoutils would try to set latin1_bin as collate?
>> There are missing MySQL international experiences on my side, but is =20
>> it
>> a good practice to rule the charset?
>>
>> Further comments on this?
>> I would prefer a database way to do this, but I wouldn't like to force
>> the user to use a charset which he doesn't know/like/can't use.
ndrlsn> This is a fair point. Would
ndrlsn> ALTER TABLE nagios_objects MODIFY name1 varchar(128) COLLATE
ndrlsn> utf8_bin NOT NULL default '';
ndrlsn> ALTER TABLE nagios_objects MODIFY name2 varchar(128) COLLATE
ndrlsn> utf8_bin default NULL;
ndrlsn> make more sense then?
ndrlsn> Can anyone with more mysql knowledge explain?
ndrlsn> Ton
ndrlsn> -------------- next part --------------
ndrlsn> An HTML attachment was scrubbed...
ndrlsn> ------------------------------
ndrlsn> Message: 2
ndrlsn> Date: Fri, 23 Oct 2009 22:49:12 -0400
ndrlsn> From: Mathieu Gagn? <mgagne@iweb
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]