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

[Ameobea]

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.

[sgrif]

It's coming from the glob import on diesel::types::*. diesel::types::ops is not internal, it's public API. we just need a more scoped import.

[alanhdu]

FWIW I just ran into this but with a column named builder.

[sgrif]

I don't think you're running into this issue. Diesel doesn't have any types or modules called builder.

[alanhdu]

Huh... ok then, I've split the builder thing off into #934.

[willmurphyscode]

It's coming from the glob import on diesel::types::*. diesel::types::ops is not internal, it's public API. we just need a more scoped import.

I'd like to work on this but I could use a hand getting started.

Am I correct in thinking that

diesel/diesel/src/macros/mod.rs

Line 275 in 6b4013d

import = [$(use $($import:tt)::+;)*];

is where we need to import something more specific? What should the import be?

Also, it looks like we're looking for imports of diesel::sql_types::* now, since there aren't diesel::types any more, after b95c9d2, correct?