Dania Es

If this is a tenant table, you can simply use `references(:tablename)` The current opts hash for `references` function in Ecto doesn't seem to support the prefix option (which would allow...

Yeah I think this will be something we see since we are defining the same module twice by loading it with ecto migrator. I'm not sure if there are any...

so changing the `Code.load_file(...)` in Ecto to `Code.require_file(...)` would prevent the file being reloaded if already loaded. I'm not sure there is a reason require_file couldn't be used in this...

@brandonparsons you should be able to ignore the warnings by putting this: `Code.compiler_options(ignore_module_conflict: true)` somewhere in your test_helpers.exs. Let me know if you run into it when compiling the dev...

Are you seeing a Postgres error, meaning a table is locked, or an elixir/erlang error? The migrators are separate processes, and the actual migrations should happen in separate schemas (obviously),...

Do you mean keeping them in the same /migrations folder, but respecting some @tag or something inside of the file? The difficulty there is that Ecto parses that folder and...

@BenMorganIO actually, the original implementation of apartmentex looked like that `use Apartmentex.Migration` which was a light wrapper around Ecto.migration. I would have to dig a little bit into the new...

I like it! how do you feel about rescuing exceptions in the error tuple format from the mongo adapter for good measure?

@cyranix @tripitakit I apologize- the Hex version is a bit behind and seems to be causing this compile error. I tried with the latest Phoenix version 1.3, and elixir 1.6.1...

Wondering if we can just import Ecto.Repo, then do something like enumerating through **info**(:functions) to patch the functions with the guard. That or proxy module that checks the guard before...