It is possible to make reference to the view prepared in the database without creating the physical table of the model defined by Wagby.
The setting method is as follows.
Even when using views, you need a primary key.(Wagby's model must specify primary key.)
If there is no primary key in the view of the existing database, please add it.
For views with updates,Disable cachingcan do.However, disabling the cache will affect performance.When the update frequency is low,I use the cache, but use the job to periodically clear the cache informationPlease also consider methods such as.
There is also a way to use "materialized view" provided by the database, while invalidating Wagby's cache.[Wikipedia...]
The materialized view is cached on the database side and the cache is also updated each time the original table is modified.So you can get the latest data.
You can use group privileges provided by Wagby by preparing the following on the view side (of the database to use).
The useridjshparam column adds "useridjshparam" to the SELECT clause of the view to be prepared and returns the data owner account.
(View name) In the $ jgroupidjshparam table, store the group ID of the group to which the data belongs.The group ID uses the primary key jgroupid of the jgroup table.
In the model defined by Wagby as "Required", please check whether NULL actually exists on the view side.Since Wagby assumes that NULL does not exist in essential items, if NULL is found, data can not be acquired correctly and an error will result.