Cory O'Daniel

I think that sounds like a good approach. Are there any other 3.8 issues you’ve run into?

fragment/1 does support positional interpolation. I am not positive if postgres supports a relation name/prefix in a prepared statement.

It is not supported by postgres to do that. I'm going to put a comment on slack to get some opinions on how best to handle this from the Ecto...

In your app do you have s fixed number of prefixes with the same schema? I’m working on a multi-tenant app (prefix per customer) now that is going to need...

So I might have an idea how this could work. If the fragment’s string was built at run time, the SQL identifiers could be interpolated into the elixir string and...

The issue is only with the fragment functions, correct? roots, parent, children, and siblings work as expected?

Was trying to be slick... This didnt work. :( Invalid syntax using a query as a prepared statement I suppose. Happens @ `(?)` ```elixir table_name_with_prefix = Arbor.CTE.prefixed_table_name( struct.__meta__, unquote(opts[:source]) )...

Yeah I was down the raw query route, but didnt want to give up composing. Are you using a fork in your code now? I'd hate to block you. I'll...

https://github.com/elixir-ecto/ecto/pull/2757 CTE support is coming! I’m going to start a refactor using this branch. Macro API will remain the same.

CTE has landed in dev: https://github.com/elixir-ecto/ecto/pull/2757