Hi again Larry

As covered in multiple tickets during the day:

1. Yes, using view you will be able to search through the table

2. You can edit only one underlying table, if you pass the proper ID while creating the view.

Hi again Larry

The ID of a row needs to be a unique auto-increment column. When you're joining multiple tables, wpDataTables needs to have the ID column for editing.

One underlying table can be edited if this ID is passed correctly, but not the other tables used in the view.

Hi again Larry

Here's an example, using wpDataTables.

wp_wpdatatable_1:

wp_wpdatatable_2:

VIEW creation:

CREATE VIEW view2 AS SELECT `wp_wpdatatable_1`.`wdt_ID`, 
                            `wp_wpdatatable_1`.`name`, 
                            `wp_wpdatatable_1`.`company`, 
                            `wp_wpdatatable_2`.`newcolumn1` 
FROM `wp_wpdatatable_1`, `wp_wpdatatable_2` 
WHERE `wp_wpdatatable_1`.`wdt_ID` = `wp_wpdatatable_2`.`wdt_ID`

Resulting table in wpDataTables generated from SELECT * FROM view2:

"newcolumn1" can't be edited, because the proper ID (wdt_ID) was passed for wp_wpdatatable_1, not wp_wpdatatable_2 it is coming from, so editing needs to be turned off for that column in order to edit or add new data. When editing is enabled for "newcolumn1" I am able to add a new row:

But it will not be seen in the table because of the WHERE clause, and the fact that wp_wpdatatable_2 doesn't have wdt_ID = 3. However, if I check wp_wpdatatable_1 in the database, it's there:

Also, if I modify wp_wpdatatable_2, and add a new row (3):

It will be associated to wdt_ID = 3 from wp_wpdatatable_1 (Google), and if I add another row in wp_wpdatatable_2 (4):

It will also show up in the wpDataTable created from the view: