Piet.Beertema@mcsun.EU.net writes: * A day or so ago I submitted a new entry for the EU.net domain, * meant to be a change on the current entry. However, I denoted * it as "EU.net" (which is the official name) instead of eu.net. * Now it appears that the updating software saw this as a *new* * entry rather than an update, in other words it doesn't work * case-independent. On the other hand the database query s/w * does work case-independent, so "whois eu.net" now gives me * two entries... * Could you remove the old eu.net entry? I dare not submit a * change for it to get it deleted, in case the updating s/w * decides to start working case-independent in that case... Sorry Piet, old, old, old software ... The new software will take care of this, but I think the new software will change everything to lowercase. I have not written this part yet, have to put some thought in it though. Anyone in the database working group has any feeling how these should be dealt with ? From a programming point of view, handling everything lowercase is much easier, I do not really want to check every single combination of lower/uppercase before I update something ... Then again, after some thinking (I usually type faster than I think ;-) the indexing is done in lowercase, and key lookups are always normalized to lowercase before a lookup. So the real question is, should entries in the database be left untouched when it comes to upper/lowercase, or should all be normalized ? -Marten