Simple to reproduce.

I have a Mysql table, two columns.  One column integer.  The second column VARCHAR(50).

I have one row.  With valid data in it.

Using wpDataTables, I created a wp-table.

Click allow Editing.

The table has the one row and displays it correctly.

I click the row, then EDIT.

On purpose, I enter a value that is longer than 50 characters.  I want to see if it truncates, or throws an error.

The response is "Success! Data has been saved".

However, the data did not change.

Attached is a word doc with images.

I found the insert throws an error when MailingAddressLine1 is longer than 50 characters.  (Good)

But the EDIT does not throw an error.  Click "edit" and change the first col... so anything longer than 50 characters, and it says "Success", but doesn't actually change the data in MySql.

Try it again with an "edit".

The data in the table is all test data, so feel free to change the row that comes up (it is dependent on VAR1) and defaults to 1.  

I don't want to make address line 1 255 characters - as that would be too long for an address.  On that note, I haven't figured out how and where to do custom validation of fields prior to insert/change.   Any suggestions?  

FYI - the MySql DDL is:

CREATE TABLE IF NOT EXISTS `Customer` ( 

`idCustomer` INT NOT NULL AUTO_INCREMENT,
`Name` VARCHAR(50) NULL,
`MailingAddressLine1` VARCHAR(50) NULL,
`MailingAddressLine2` VARCHAR(50) NULL,
`MailingAddressCity` VARCHAR(50) NULL,
`MailingAddressState` VARCHAR(50) NULL,
`MailingAddressZip` VARCHAR(20) NULL,
`PhysicalAddress1` VARCHAR(50) NULL,
`PhysicalAddress2` VARCHAR(50) NULL,
`PhysicalAddressCity` VARCHAR(50) NULL,
`PhysicalAddressState` VARCHAR(50) NULL,
`PhysicalAddressZip` VARCHAR(20) NULL,
`PhysicalAddressPhone` VARCHAR(50) NULL,
`FrequencyFacilityInspections` VARCHAR(50) NULL,
`FrequencyInvoicing` VARCHAR(50) NULL,
`LUSR` BIGINT NULL,
`LUDT` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (`idCustomer`))
ENGINE = InnoDB
COMMENT = ' ';

Thanks for your help.

created view.  Same results.

This is such a simple problem.  Let's create it on your end.

CREATE TABLE Customer 
( `idCustomer` INT NOT NULL AUTO_INCREMENT, 

`Name` VARCHAR(50) NULL
PRIMARY KEY (`idCustomer`))
ENGINE = InnoDB
COMMENT = ' ';

In wpDataTables, create a wpDataTable from SQL table Customer.  

• Make it edittable.  
• Use the idCustomer as the id column.
• Click on the column settings for Name, make it String , and editable One-line-edit.
• No need to see the id column, as it's auto-increment.  I leave it as Integer, and under EDIT - none.

1)  Now, add a row with a Name.

2) click on the row, click on Edit.  On purpose, enter a name with a length longer than 50 characters.

When I do this, I get "Success", but nothing happened.  The update did not occur in the database.

note: I'm using wpDataTables with a database that is pre-defined.  The solution is not to make every text field unlimited length so that it works with wpDataTables.

Bottom line: even if I do something wrong in setup, wpDataTables should NEVER give a "success" return status, when it was not.

corrected SQL in response below (missing a comma):

CREATE TABLE Customer  ( `idCustomer` INT NOT NULL AUTO_INCREMENT, 

`Name` VARCHAR(50) NULL, PRIMARY KEY (`idCustomer`)) ENGINE = InnoDB COMMENT = ' ';

Yes, I tried the view.  Same problem.

Did you try the simple CREATE TABLE with a varchar(50) and test it yourself on your platform?  Details below with instructions on how to exactly recreate this problem.

What i have learned so far is that inserts (click NEW) show an error when MySQL throws an error (when given a string too long).

However, it appears that errors thrown during the update (EDIT) always say "Success", even when not.  I'd guess the UPDATE source code isn't checking the MySQL return code correctly...

Thanks - Dan

Thanks for recreating this.  

I suspect the problem is the MySql return code isn't being checked properly on return from an "update".  

Other scenarios that probably have the same problem are:

• What if the table is locked on the update and the update can't be performed?
• What if a referential integrity error was triggered, and the update wasn't performed?
• Try to change a field to null, when null is not allowed.

Thanks for looking into this, and I look forward to it's resolution.

Dan