Hi, first off, thanks for the great plugin! The documentation's great, and I got set up with a working webpage for trying out Editor couple days into my trial. There's been some issues, but mostly nothing I couldn't work around.

One thing that kept recurring though was that if I have an SQL table with a primary key column of Decimal type, Editor can't seem to handle it. The change goes through to the back-end, but then Editor throws an error, row 342 in editor.js, 'Primary key element is not available in the data set'. The table is unusable by Editors front-end after this, it fails to load every time until I go remove the offending value.

Looking at the code, there's this null check which seems to discard the valid zero values a few rows above that previously mentioned row:

            if (flat) {
                val = row[column] ?
                    row[column] :
                    null;
            }

I can probably make quick fixes for my own setup here, but the handling here needs improvement. Maybe add another branch for extended handling if the primary key column is any number-type?

I use this [email protected] sample to test "File upload" I get "No data detected. Have you used {extended: true} for bodyParser?"
But I use [email protected] test "File upload" is success.
It's may have bug?

GHSA-4jv9-3563-23j3

node_modules/datatables.net-editor-server/node_modules/knex
node_modules/knex
  datatables.net-editor-server  *
  Depends on vulnerable versions of knex
  node_modules/datatables.net-editor-server