从 MySQL 触发器动态更新交叉表视图

发布于 2024-10-19 06:42:06 字数 1934 浏览 0 评论 0原文

我正在尝试对 MySQL 服务器上动态生成的交叉表视图中的某些数据进行反规范化。由于这里有一个有用的答案,我已经成功创建了一个生成此交叉表视图的存储过程。

这是我的过程:

DELIMITER $$

CREATE PROCEDURE `PartFlow`.`DimMatTab` ()
BEGIN
    SET @cols = (
    SELECT
    GROUP_CONCAT(DISTINCT
        CONCAT(
            '\nSUM(IF(dimension_id = ',
            dimension_id,
            ', value, NULL)) AS ',
            name
        )
    ) as column_list
    FROM PartFlow.tDimMatMap
    JOIN PartFlow.tDimension
        on tDimension.id_dimension = tDimMatMap.dimension_id
    );

    SET @sql = CONCAT(
        'CREATE OR REPLACE VIEW `PartFlow`.`vDimMatTab` AS '
        'SELECT material_id, ',
        @cols,
        ' FROM tDimMatMap ',
        'GROUP BY material_id;');
    PREPARE stmt FROM @sql;
    EXECUTE stmt;
END

生成一个包含此查询的视图:

select
`material_id`
,sum(if((`dimension_id` = 2),`value`,NULL)) AS `Width`
,sum(if((`dimension_id` = 3),`value`,NULL)) AS `Height`
,sum(if((`dimension_id` = 5),`value`,NULL)) AS `Thickness`
from `PartFlow`.`tDimMatMap`
group by `material_id`

我希望在对 tDimMatMap 进行任何更改时更新该视图,以便该视图始终包含正确的交叉表列。我已尝试在此源表上的任何插入、更新或删除操作上触发该过程。这是我的触发器代码:

create trigger update_view_iMat after insert on tDimMatMap
for each row call DimMatTab();$$

create trigger update_view_uMat after update on tDimMatMap
for each row call DimMatTab();$$

create trigger update_view_dMat after delete on tDimMatMap
for each row call DimMatTab();$$

在我看来,这是一个完美的设置,但是当我尝试编辑 tDimMatMap 表时,我收到错误消息“存储函数或触发器中不允许使用动态 SQL”。有什么办法可以解决这个问题吗?我是否从错误的角度处理问题?我只是想确保我的交叉表视图始终包含 tDimMatMap 表中列出的每个唯一“dimension_id”的列。

我从多个客户端前端访问这些数据,因此这种集中式解决方案似乎是正确的。我确信有些人会说我应该在服务器外部生成 SQL 代码,或者运行过程来获取数据而不创建视图,但我无法在客户端内动态更新此视图,也无法通过调用我的客户内部的程序。最重要的是,该视图将连接到某些应用程序中的其他视图和表,因此创建视图非常重要。

I'm attempting to de-normalize some data in a crosstab view which is dynamically generated on the MySQL server. Due to a helpful answer here, I've successfully created a stored procedure which generates this crosstab view.

This is my procedure:

DELIMITER $

CREATE PROCEDURE `PartFlow`.`DimMatTab` ()
BEGIN
    SET @cols = (
    SELECT
    GROUP_CONCAT(DISTINCT
        CONCAT(
            '\nSUM(IF(dimension_id = ',
            dimension_id,
            ', value, NULL)) AS ',
            name
        )
    ) as column_list
    FROM PartFlow.tDimMatMap
    JOIN PartFlow.tDimension
        on tDimension.id_dimension = tDimMatMap.dimension_id
    );

    SET @sql = CONCAT(
        'CREATE OR REPLACE VIEW `PartFlow`.`vDimMatTab` AS '
        'SELECT material_id, ',
        @cols,
        ' FROM tDimMatMap ',
        'GROUP BY material_id;');
    PREPARE stmt FROM @sql;
    EXECUTE stmt;
END

Which produces a view containing this query:

select
`material_id`
,sum(if((`dimension_id` = 2),`value`,NULL)) AS `Width`
,sum(if((`dimension_id` = 3),`value`,NULL)) AS `Height`
,sum(if((`dimension_id` = 5),`value`,NULL)) AS `Thickness`
from `PartFlow`.`tDimMatMap`
group by `material_id`

I'd like the view to be updated on any changes to tDimMatMap, so that the view will always contain the right crosstab columns. I've tried triggering the procedure on any insert, update, or delete on this source table. Here is my trigger code:

create trigger update_view_iMat after insert on tDimMatMap
for each row call DimMatTab();$

create trigger update_view_uMat after update on tDimMatMap
for each row call DimMatTab();$

create trigger update_view_dMat after delete on tDimMatMap
for each row call DimMatTab();$

In my mind, this is a perfect setup, but when I try to edit the tDimMatMap table, I get the error message, "Dynamic SQL is not allowed in stored function or trigger". Is there any way to get around this? Am I approaching the problem from the wrong angle? I simply want to make sure that my crosstab view always contains a column for every unique "dimension_id" listed in the tDimMatMap table.

I am accessing this data from multiple client front-ends, so this centralized solution seems right. I'm sure that some would say that I should generate my SQL code outside the server, or run the procedure to grab my data without creating a view, but I cannot dynamically update this view within my clients, nor can I query by calling a procedure within my clients. Most importantly, this view will be joined to other views and tables in certain applications, so creating the view is pretty important.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文