infer_schema! fail to find .env in local project if it is inside a workspace

[limira]

Setup

Versions

• Rust: 1.26
• Diesel: 1.2.2, diesel_infer_schema: 1.2.0
• Database: Sqlite
• Operating System Fedora 27

Feature Flags: ["sqlite"]

Problem Description

What are you trying to accomplish?

I have a workspace like this:

workspace\
    |---- Cargo.toml
    |---- .env (.env at workspace root)
    |---- projects\
            |---- project1\
                    |---- Cargo.toml
                    |---- .env (.env at project root)
                    |---- src\...

If I put DATABASE_URL in .env at project root

• ::std::env::var("DATABASE_URL") found it 👍 , but
• infer_schema("dotenv:DATABASE_URL") give error 👎 :

1 | infer_schema!("dotenv:DATABASE_URL");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = help: message: called `Result::unwrap()` on an `Err` value:
    "Failed to load environment variable DATABASE_URL:
    environment variable not found"

If DATABASE_URL is in .env at workspace root: infer_schema works

What is the expected output?

infer_schema should works with .env inside project folder

Checklist

• I have already looked over the issue tracker for similar issues.

[weiznich]

We are relaying on the dotenv crate for handling .env files. So this should probably be reported there.

[limira]

I reported this to dotenv. It is not an issue in diesel itself, but I think it is useful to leave this open, because infer_schema does not actually work as expected.
We will update the version of dotenv in [dependencies] and close this when the issue in dotenv get fixed.

[daboross]

I believe this is an issue in diesel - it uses dotenv, but the error is in how diesel is using dotenv.

The method it's using, dotenv(), uses the current working directory to find .env files. However, it's being used here inside a procedural macro (in infer_schema_macros), and procedural macros are always run in the workspace root, rather than the crate root.

If this is deemed a real issue, the only way to fix this will be to have diesel change the working directory or use a different function from dotenv to load the file.

[limira]

@weiznich, @sgrif, what do you think?
I actually can put the DATABASE_URL into .env at the workspace root. But it is very nice if we can put it into .env at the crate/project root, because it is only use for that specific crate.

Edit:
I noticed that you are deprecated infer_schema, so, just ignore this.