Search

Thanks, fbas. Your advice was very helpful. I think I've found the solution. New rows should be added in the following mode: [code] $('#example').dataTable().fnAddData(json.aaData, false); $('#example').dataTable().fnDraw(false); [/code]

Thanks kktos. I do already use this, having spotted that IE ignores standards mode for pages served from localhost without it.

10 rows in default mode [code] $('#table_id').dataTable();[/code], it is

you to use no-conflict mode I wonder what they

pagination buttons in full_number_paging mode don't seem to be

works in my development mode on rails, but fails

DataTables in server-side processing mode doesn't have access to

Have you read and tried the solution here? http://www.datatables.net/forums/discussion/5481/bug-ghost-columns-when-generating-large-tables/p1 This solution definitely solved the known bug in IE9 (not in datatables, but in IE9), BUT whether it can also do anying for you in quirks mode, is another question entirely...

to get oci_fetch_array to only return a numeric array, give it a $mode = OCI_NUM. else it returns an array with both associative keys and integer keys. array oci_fetch_array ( $statement, OCI_NUM ) --EDIT-- or simply call oci_fetch_row ( $statement ). same thing.

my table in this mode you can see below,