- SQL_CALC_FOUND_ROWS was used to try and speed the queries up, and that
works well for MySQL, but it confuses anyone who tries to modify this
script for other databases.
- Field escaping should possibly be considered in future as well
- This is primarily for the forum
- This is quite common in markdown extensions now and has plenty of
backup from Stackoverflow etc to suggest it is a good idea. About time
I did it as well!
- SQL_CALC_FOUND_ROWS was used to try and speed the queries up, and that
works well for MySQL, but it confuses anyone who tries to modify this
script for other databases.
- Field escaping should possibly be considered in future as well
- Many thanks to jthsiao at Google for the initial integration work
- Example added
- CSS decompiled to SCSS as it has a bit more structure
- Removed the TableTools integration since TableTools is now retired
- Reduce the gap between the table grid components
- Use single arrow for previous / next paging
Weirdly the UIKit documentation examples don't appear to match up with
what you get if you actually use the UIkit distribution code - see
https://github.com/uikit/uikit/issues/1739 . As such the UIKit /
DataTables example doesn't look as nice as might be expected.
- Bootstrap 4 is currently in beta so things can, and probably will
still change. Bootstrap 4 packages for DataTables won't be made
available until at least a beta release of Bootstrap 4.
- A few things have changed in Bootstrap 4 and rather than trying to
make the exisiting Bootstrap files work for both BS3 and BS4 it makes
sense to offer both. We'd need to detect which version of BS is loaded
and that can be quite unreliable (and delayed since the body would
need to be available).
- Pagingation requires a couple of classes, but no change in structure
- BS4 don't include icons any more, so need to use UTF8 arrows to show
sorting (don't particularly want other dependencies, although it is
easy to add with CSS if you want more icon control)
- Outstanding issue: The select element for paging control is not of a
consistent height with the search input. This appears to be a
Bootstrap issue: https://github.com/twbs/bootstrap/issues/17194
doesn't effect the DataTables demos since the inserts all have values
for this field. It is done for Editor which can use this table for
editing and it simplifies the MySQL aspect.
Rational for this is that the number renderer expects a number
input, not HTML, but if non-numeric input is given the value is just
returned (now escaped) - for example an empty string.
