flowable 和 activty工作流 使用视图方案解决系统内部用户、组、用户和组关联
生活随笔
收集整理的這篇文章主要介紹了
flowable 和 activty工作流 使用视图方案解决系统内部用户、组、用户和组关联
小編覺得挺不錯的,現(xiàn)在分享給大家,幫大家做個參考.
開源項目若依項目集成flowable工作流用戶解決方案
-- ---------------------------- -- View structure for act_id_group -- ---------------------------- DROP VIEW IF EXISTS `act_id_group`; CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `act_id_group` AS select `r`.`role_key` AS `ID_`,NULL AS `REV_`,`r`.`role_name` AS `NAME_`,'assignment' AS `TYPE_` from `sys_role` `r` ;-- ---------------------------- -- View structure for act_id_membership -- ---------------------------- DROP VIEW IF EXISTS `act_id_membership`; CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `act_id_membership` AS select (select `u`.`user_name` from `sys_user` `u` where (`u`.`user_id` = `ur`.`user_id`)) AS `USER_ID_`,(select `r`.`role_key` from `sys_role` `r` where (`r`.`role_id` = `ur`.`role_id`)) AS `GROUP_ID_` from `sys_user_role` `ur` ;-- ---------------------------- -- View structure for act_id_user -- ---------------------------- DROP VIEW IF EXISTS `act_id_user`; CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `act_id_user` AS select `u`.`user_name` AS `ID_`,0 AS `REV_`,`u`.`nick_name` AS `FIRST_`,'' AS `LAST_`,`u`.`email` AS `EMAIL_`,`u`.`password` AS `PWD_`,'' AS `PICTURE_ID_` from `sys_user` `u` ;開源項目GUNS項目集成flowable工作流用戶解決方案
-- ---------------------------- -- View structure for act_id_group -- ---------------------------- DROP VIEW IF EXISTS `act_id_group`; CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `act_id_group` AS SELECT `r`.`role_code` AS `ID_`, NULL AS `REV_`, `r`.`role_name` AS `NAME_`, 'assignment' AS `TYPE_` FROM `sys_role` `r`;-- ---------------------------- -- View structure for act_id_membership -- ---------------------------- DROP VIEW IF EXISTS `act_id_membership`; CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `act_id_membership` AS SELECT( SELECT `u`.`account` FROM `sys_user` `u` WHERE ( `u`.`user_id` = `ur`.`user_id` ) ) AS `USER_ID_`,( SELECT `r`.`role_code` FROM `sys_role` `r` WHERE ( `r`.`role_id` = `ur`.`role_id` ) ) AS `GROUP_ID_` FROM `sys_user_role` `ur`;-- ---------------------------- -- View structure for act_id_user -- ---------------------------- DROP VIEW IF EXISTS `act_id_user`; CREATE ALGORITHM=UNDEFINED DEFINER=`root`@`localhost` SQL SECURITY DEFINER VIEW `act_id_user` AS SELECT `u`.`account` AS `ID_`,0 AS `REV_`,`u`.`nick_name` AS `FIRST_`,'' AS `LAST_`,`u`.`email` AS `EMAIL_`,`u`.`password` AS `PWD_`,'' AS `PICTURE_ID_` FROM `sys_user` `u`;補(bǔ)充:說一下為什么不用user_id role_id關(guān)聯(lián)呢?由于工作流act_user表中的_ID對應(yīng)的是用戶賬戶,因此,都采用以上方案。
總結(jié)
以上是生活随笔為你收集整理的flowable 和 activty工作流 使用视图方案解决系统内部用户、组、用户和组关联的全部內(nèi)容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: MYSQL用存储过程创建百万级测试数据表
- 下一篇: Windows下安装ab