It's getting more complex now. Shouldn't this be predicted by RC? I'm kind of lost now. Even if I can't make search work properly, I would expect at least the date to be stored (and shown) as entered. IMHO, this is certainly a bug. This is also proven by the fact that if, for example, we enter a date which is out of bounds in the stored format (for example, if i enter '25/12/1980' nothing will be stored in the contact, because it will first be converted to 1980-25-12' which clearly is invalid.
In any case, is it possible to prohibit datepicker to add slashes? I did not add the slashes, it did.