Nicolas Brassard

> I'd just have separate Date and Datetime fields. I think this is not a good idea. timestamps always contains seconds and it's only a mater of formatting. (input formatting...

All dates are timestamps. Even if it is a _date only_ field, the timestamp will contains the hours, minutes and seconds. So 2015-08-28 (no time) is actually 2015-08-28 00:00:00.000

How would you store it ? It needs to be stored as a timestamp (MySQL datetime is a timestamp). Saving it as a string is not a good idea IMHO.

> Maybe for MySQL internally, Yes that's what I meant. DATE is a truncated timestamp (for saving storage space). But since hard drives are so cheap, I do not see...

> Just thought that it might make things a bit more clear. It may, but for me, it's not maintainable 1. Lots of code duplication (unless both fields are provided...

This will break lots of thing. We would need to add a way to be able to add text in between child nodes.

Agreed. Can't wait to implement this.

@michael-e I think ALL XMLElement should do it... but this would break even more things...

Yes, we change from opt-in to opt-out. And would hurt perf.

First because we would need to render things from the bottom up (instead of top-down like we do) and because we will need to call html entities a lot. Should...