DAF ID3000
New member
Dear Eugenio,
I use a lot of views I design in MariaDB as datasources to pages in Dadabik. This allows me to use SQL possibilities (dynamically calculated fields, subqueries, etc.) to enhance data I show in Dadabik grids.
But the dark side of this is that I loose updatable and insertable behaviors for these views and I must deal with two different pages in Dadabik, the first one based on my enhanced view to get all the informations I want to display in the grid, and the second one based on the source table to allow insert and update actions.
I managed with custom buttons from enhanced view page to link to the insert_form of the source table but the target page after inserting becomes the source table page and the user losts himself :-( So it's far from perfect...
My idea would be to add on the 'Pages based on view' definition a new field containing the target table (or updatable view) to update/insert to (by default it could be the same as 'view name' and we get the same behavior as now).
Upon the validation click on insert or update form, the only change in Dadabik behavior (for pages based on views) would be to replace the main view name by the new 'target table' field.
Of course, the reponsability of using the same fields names between the main view and the target table would be on the dadabik developper hands. He would have to show on insert/update form only fields which exist in both view and table to allow INSERT/UPDATE SQL orders to run successfully...
IMHO, this update would really give new exciting possibilities, even if your Dadabik framework is already one of my favourite tools ! ;-)
Thanks in advance to tell me what is your opinion.
KR
--
Gilles
I use a lot of views I design in MariaDB as datasources to pages in Dadabik. This allows me to use SQL possibilities (dynamically calculated fields, subqueries, etc.) to enhance data I show in Dadabik grids.
But the dark side of this is that I loose updatable and insertable behaviors for these views and I must deal with two different pages in Dadabik, the first one based on my enhanced view to get all the informations I want to display in the grid, and the second one based on the source table to allow insert and update actions.
I managed with custom buttons from enhanced view page to link to the insert_form of the source table but the target page after inserting becomes the source table page and the user losts himself :-( So it's far from perfect...
My idea would be to add on the 'Pages based on view' definition a new field containing the target table (or updatable view) to update/insert to (by default it could be the same as 'view name' and we get the same behavior as now).
Upon the validation click on insert or update form, the only change in Dadabik behavior (for pages based on views) would be to replace the main view name by the new 'target table' field.
Of course, the reponsability of using the same fields names between the main view and the target table would be on the dadabik developper hands. He would have to show on insert/update form only fields which exist in both view and table to allow INSERT/UPDATE SQL orders to run successfully...
IMHO, this update would really give new exciting possibilities, even if your Dadabik framework is already one of my favourite tools ! ;-)
Thanks in advance to tell me what is your opinion.
KR
--
Gilles
Attachments
Upvote
0