What's new

Version 1.3 is a milestone release and has numerous changes in both design and functionality.

Determines the propper default value for empty fields based on the table schema.
Support for persistent connections. See set_db_params().
Better support for case-insensitive database servers installations.

It is now possible to show a confirmation dialog before deleting a record. See set_confirm_delete().
It is now possible to add custom $_GET arguments to be appended to all generated links. See set_arg().
The message shown when an action is blocked is now contained in a template, making it customizable. See the folder structure for more info.
All configuration variables are now outside of the main kDataGrid class, making them easier to override and integrate into existing architectures.
Caching support. See set_cache() and set_cache_clean_actions().
Improved default template.
Fixed a bug where an error was thrown when the grid was empty.

Version 1.2 is a milestone release and has numerous changes in both design and functionality.

Added support for Oracle, SQL Server and Postgres. Reference: set_db_type()
It is now possible to explicitly set column widths. Reference: set_columns_width()
It is now possible to change the CSS Id and Class attributes of the grid. Reference: set_css_class() and set_css_id()
It is now possible to block specific actions (data-editing pages) from being displayed. Reference: block_actions()
Fixed a bug with the set_columns_maxlength() where lengths were not correctly parsed under some conditions.

Version 1.1 is a milestone release and has numerous changes in both design and functionality.

Data Editing. Automatically generates view/add/edit/delete pages for easy data manipulation.
Template Engine. kDataGrid 1.1 uses a template engine to generate the grid and data-editing pages. This allows for easy and detailed look-and-feel customization.
Sorting. Sorting is now available in the front-end by clicking on column headers.
Custom column formatting. Provides custom formatting rules for any column in a resultset; especially useful for formatting currency or e-mail fields.
Custom column lengths. Limits the maximum number of characters displayed for any field; useful for truncating links, street addresses or lengthy text descriptions.
Edit-in-place. Edit-in-place functionality is now handled automatically.