Error after upgrading from 1.0.7 to 1.0.8: database prefix information being lost

[sevenseacat]

This might be a bit vague but I believe it's to do with the batching functionality here #93 (which is what I upgraded to get).

My app uses Postgres schemas for multi-tenancy, and in 1.0.7 this worked fine. As far as I can tell, I haven't needed to manually specify the schema for Dataloader anywhere - my Absinthe resolvers use the correct prefix (eg. loading data using Repo.one(query, prefix: "my_prefix"), and then Dataloader magically does the rest.

Upon upgrading to 1.0.8 for the new lateral join queries, now the database prefix information is missing when preloading data (and thus erroring because the default schema has no data in it).

If there's any more information I can provide, please let me know!

[sevenseacat]

Fixed by #107