allow setting of referential integrity in database
Posted: 2020-12-12 08:44
Hi,
I know, it's a big wish, as AG tries to support multiple backend databases. Still.
It would be a great help and time safer, that if I set a field to be a lookup from another table, that I can also define directly in AG that there should be
referential integrity set with update and delete options (on update .... / on delete ...).
The 'on delete' is somehow realized in AG as the frontend user does not notice anything, 'on update' the same: The users simply sees the current values.
But - for the sake to clean and correct data in the database I am always editing the database structure for such tables by hand afterwards and add referential integrity. See my image - it can be daunting with so many fields, and this is just one table
Olaf
I know, it's a big wish, as AG tries to support multiple backend databases. Still.
It would be a great help and time safer, that if I set a field to be a lookup from another table, that I can also define directly in AG that there should be
referential integrity set with update and delete options (on update .... / on delete ...).
The 'on delete' is somehow realized in AG as the frontend user does not notice anything, 'on update' the same: The users simply sees the current values.
But - for the sake to clean and correct data in the database I am always editing the database structure for such tables by hand afterwards and add referential integrity. See my image - it can be daunting with so many fields, and this is just one table
- foreignkeys.png (8.03 KiB) Viewed 3007 times