Compilation with `infer_schema!` panics when table has column named `ops` · diesel-rs/diesel#851

(5 comments) (0 reactions) (1 assignee)Rust (12,054 stars) (1,003 forks)batch import

assignedbughelp wanted

説明

Somewhere in the macro expansion, there is code that imports ops from within diesel. If a column in a database is named ops, this causes conflicts within the macro.

I think that putting a note somewhere that this could happen may be enough; however, prefixing the internal variables or module names to something like _table_ops or something similar would be a more permanent solution.

コントリビューターガイド

技術スタック: rust
領域: backenddatabase
Issue 種別: bug
難度: 3
推定時間: 1-2 days
活動状況: blocked
明確さ: clear
前提条件: Rust macrosDiesel ORM
初心者向け度: 45
調査方針: Investigate the `infer schema!` macro implementation in the diesel codebase. The issue arises because the macro imports `ops` from diesel internally, conflicting with a table column named `ops`. A possible fix is to prefix internal variable names like ` table ops` to avoid name conflicts. Key files to look at include the macro definitions in the `diesel` crate.