The changelog for the SQLite Editor

The generation of the query-string has been centralised to a single function. This makes it easier to update and, if necessary, change.

Fixed a bug where the row hover color wasn't being applied to all of the columns when the sql_delete and checkboxes option were both falsey.

When you delete items in the editor, the URL manipulation has been massaged so that spurious query-string crumbs are not added and the URL doesn't grow out-of-control.

The source code has been significantly updated by changing the prefix that many function names had - the prefix "sqliteeditor_" has been changed to "editor_" .The sqlite name has been removed from other places too - for example the query-string parameter names. So now there shouldn't be any trace of the sqliteeditor name in the code.

When the editable_callback_url option is used, the POST data that's sent to the server has been updated. The parameter names have now also been changed to "editor_" instead of "sqliteeditor_" and the id parameter is now called "editor_id". The "database_name" parameter has been removed.

There's now support for various HTML5 form control elements: date, datetime, time, number and color You can specify these by setting the editable_types property to the relevant type.

There's a new editable_types option which alows you to specify the type of HTML form input that you want to see when editing a cell. The various types include: text (the default), date, time, datetime, color, number and select. The editable_options option (which is used when you stipulate that an editable column is a select dropdown list) can take several formats, including a function, an array, a CSV string or an SQL query. The function option can be used when you need a different set of options for each entry in the table.

Rows can now be selected by clicking on the entire row - not just the checkbox in that row. There's now two functions: editor_selectrow(tr) and editor_togglerow(tr) which you can use to check or uncheck rows.

The ordering of the results is now case-insensitive by default. There's a new property, though, ordering_case which defaults to false and if you change this to true the ordering will be done in a case-sensitive manner. Remember though, that this does mean that you will see all of the upper-case entries before the lower-case entries.

The search has been updated to use the SQLite GLOB functionality instead of the LIKE functionality. This makes it a bit more versatile for you so you can search for data in a few more ways. You can read about the ways that you can search in the search section above.

You can now sort the data by clicking the column headers. You can click the header multiple times to cycle through ascending, descending and not sorted. If you use the callbacks to alter the output then the resulting sorting may be unpredictable.

There was some mixing of the styles property where it was called style (no 's') in some places. This has been rectified and the correct term, styles, is what you should use.

A search was added that enables you to search within the results. Internally, a LIKE query is performed doing this style of match %word1% AND %word2% AND %word3% etc. The search-clause is added to your select query when the user performs a search.

This was the initial release of the SQLite Editor for PHP software. Read through the documentation - specifically the API documentation - to learn about the features that are available to you.