This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rdbms:mysql:tables [2011/04/07 16:25] doc |
integration:rdbms:mysql:tables [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 75: | Line 75: | ||
| Omnidex table declarations can reference MySQL Views. Omnidex will retrieve from the MySQL view just as though it is a table. MySQL Views can be used to provide different views of the data, appropriate for the application. | Omnidex table declarations can reference MySQL Views. Omnidex will retrieve from the MySQL view just as though it is a table. MySQL Views can be used to provide different views of the data, appropriate for the application. | ||
| - | When referencing a MySQL view, it is necessary to declare a UNIQUE constraint. This requirement for the UNIQUE constraint is independent of any PRIMARY or FOREIGN constraints, discussed in the next page. The UNIQUE constraint tells Omnidex how to uniquely identify a row. When Omnidex retrieves individual rows, it will use this unique value; therefore, it is important that access to this column (or columns) be properly indexed in the underlying table. | + | When referencing a MySQL view, it is necessary to declare a UNIQUE constraint. This requirement for the UNIQUE constraint is independent of any PRIMARY or FOREIGN constraints discussed in the next page. The UNIQUE constraint tells Omnidex how to uniquely identify a row. When Omnidex retrieves individual rows, it will use this unique value. Therefore, it is important that access to this column (or columns) be properly indexed in the underlying table. |
| **MySQL CREATE VIEW Statement** | **MySQL CREATE VIEW Statement** | ||