mirror of
https://github.com/DataTables/DataTables.git
synced 2024-11-29 11:24:10 +01:00
16dea34d8c
- Automatic column type detection was a real weak point of v1.9- - it did basically work, but if you then updated a row that didn't match the current data type it would always end up as a string. A good example of this is the ambiguous date "06-06-13" (is it dd-mm-yy or mm-dd-yy?). If it was detected as dd-mm-yy and then you add '05-20-13' to the column (or update an exisiting cell), the type would not match the exisiting value that thus failover to a string. - Type detection is now more rigorous, but still optimised (since it has the potential to take up a significant amount of time). When a row is added or updated, or a cell is updated, the exisiting type is removed from the target column(s) and then, before sorting or filtering, the _fnColumnTypes function checks to see if any column needs to be type detected and do so if needed. This approach allows multiple rows to be added (for example) before the draw is performed and the type actually needs to be calculated. - In future I'd like to have a 'data-ready' type event which will tell DataTables, and any of its components that something wants to work with the data in the table and it should prep the data. The counterpart would be a 'data-invalid' flag which would be set on update, add etc so it knows when an update is needed. |
||
|---|---|---|
| .. | ||
| css | ||
| images | ||
| js | ||
| unit_testing | ||