Call module specific function not working?

[quinnj]

I recently updated my Julia build, 614b2eff2, and noticed there were some additional methods added to connect, particularly one that takes a single string as an argument. It's never been a conflict before, but the ODBC package also has a connect function that is defines with a single string argument for the DSN, and usr::String="", pwd::String="" as named arguments.

I noticed the conflict as I tried to run a script and the Base.connect was called as one would expect. I thought this would eventually happen, but I tried to explicitly call ODBC.connect and Base.connect was still called. Is this expected? I thought fully referencing a module before a function made sure the module function would be called.

julia> Base.connect("SHC")
ERROR: connect: socket operation on non-socket (ENOTSOCK)
 in yield at multi.jl:1415

julia> ODBC.connect("SHC")
ERROR: connect: socket operation on non-socket (ENOTSOCK)
 in yield at multi.jl:1415

julia> @which ODBC.connect("SHC")
connect(path::Union(ASCIIString,UTF8String)) at stream.jl:817

[Keno]

are you importing the connect method in ODBC?

[quinnj]

Yes.

import Base.show, Base.connect, Base.Chars

[Keno]

that's your problem right there ;)

[StefanKarpinski]

That's an unfortunately named function. ODBC probably should either not export it or call it something that doesn't clash with a fairly important function in Base. Either that or just add methods to Base.connect if appropriate.

[quinnj]

Ah.....I think I see now. I think the solution will be to not export connect and users can call ODBC.connect.