Hi!<br><br>Is it a good idea avoid nil in magma indexes?<br>This question rised when I tried MaDateIndex. Until this moment, I used String or Integer indexes having care to answer allways a String (an empty string if the object is nil) and an&nbsp; Integer (a zero if nil). But with dates there is a conceptual problem: there is not a null date. In some applications, business stuff, for example, you can think in an ovbiously unused date (01-01-1500, for example) that acts as a null date. It&#39;s a little dirty, but it would work. But in other applications every possible date has a meaning. And if the object could be inexistent in some cases, you have no choice: it&#39;s nil. 
<br>That&#39;s my case, and I&#39;m forced to use a StringIndex, converting the dates to Strings, answering an empty string if the object is nil. That&#39;s really dirty.<br>Would&#39;nt be better if magma indexes just ignore nil objects? Is it a requirement for magma that every object from a MagmaCollection must be present in all indexes?
<br>I hope there is something I misunderstood and there is a more elegant solution.<br><br>Regards<br>Norberto<br><br>