diesel-rs/diesel

Compilation with `infer_schema!` panics when table has column named `ops`

Open

#851 建立於 2017年4月6日

在 GitHub 查看
 (5 留言) (0 反應) (1 負責人)Rust (12,054 star) (1,003 fork)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
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Rust macrosDiesel ORM
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
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.
Compilation with `infer_schema!` panics when table has column named `ops` · diesel-rs/diesel#851 | Good First Issue