Search

processed and the client-side table appropriately updated.

in two or more table columns, rather than just

your database with the tables and data required for

with get_db() as conn: table = DataTable(db, "staff").columns( Column("first_name"), Column("last_name"),

be applied to the table simply by calling Editor.where()

session variable Editor::inst( $db, 'table' ) ->fields( ... ) ->validator( function ( $editor,

session variable Editor::inst( $db, 'table' ) ->fields( ... ) ->validator( function ( $editor,

checks the host Editor table, not any other database tables - so if you have

for a read only table (DataTable class): Column::inst( 'start_date'

information to a database table that details what user

You still need to use an if statement to check the settings.nTable.id value for the table you want the plugin to work with. The next major version is Datatables V2 which is not out yet. Kevin

It looks like you need to remove the header rows explicitly as they were added outside of DataTables's control. You can do that with: $('table tr').remove(); See updated example here: http://live.datatables.net/zigijote/2/edit Colin

I'm noticing a lag as the inner table gets rendered. Since I'm doing DataTables only, I'll have to test that out and see whether there isn't much of a lag.

it messes up the table if I leave it

other columns in the table, it can actually result

listed in the compatibility table (thx Kevin) and I

Previously, with a coded table, I could either run

might be confusing which table will be filtered. The

how you're initialising the table - I imagine you're initialising

The first parameter passed into the $db->insert() method is the database table that the insert will operate on. You can modify that as you need. Allan