-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arc_ecto not working with Ecto 3 #272
Comments
You can force override ecto/ecto_sql via |
Thank you, it would be great if it can be fixed next week. I tried override: true but then arc_ecto can't create date function structures, so it dies, and also cast_attachments/3 throws an error. It seems the differences between Ecto 2 and Ecto 3 break it. Its a great solution though to make trivial what would otherwise require quite a bit of boilerplate. |
If you bump arc_ecto to 0.11.1, I think this will resolve the issue. |
Thank you for the update, I will try that.
… On Nov 30, 2018, at 4:40 PM, David Bernheisel ***@***.***> wrote:
If you bump arc_ecto to 0.11.1, I think this will resolve the issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#272 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANAKcOPC2ynOhJc4fnQUhVt49kEQ6Sodks5u0dAXgaJpZM4YmMnj>.
|
Seems that the bug with cast_attachments/3 is not fixed by 0.11.1 and Ecto 3.0. Any workaround ideas? |
@bnenu Can you clarify the issue? I'm not seeing any compatibility issues with arc_ecto and Ecto 3.0 with arc_ecto v0.11.1+ |
|
Here is the error and here is my asset schema and changeset
I have to say that I am fairly new to elixir and I had a previous project that used arc with a similar setup that worked with previous versions of Ecto, Arc and Arc.ecto. This app is part of an umbrella project if that is relevant. Please excuse my mistake if this ends up being something else. |
What precisely is on line 51 of file |
line 51 assets.ex
One other thing is that I construct the file passed myself %{ filename: "image.jpeg" , binary: ...}, as I get the image body in base 64 encode string and I parse the binary with Base.decode64!, if that is relevant for the case. |
For note, code fences are done with 3 `'s, like:
However, this is probably the reason, It looks like it would be a pretty simple fix though, just need to add the proper case to https://github.com/stavro/arc_ecto/blob/master/lib/arc_ecto/schema.ex#L35 so I'd say submit a PR or at least open an issue ticket at https://github.com/stavro/arc_ecto itself. :-) Based on the existing arc_ecto code though, I'm not sure how that would have ever worked, so this doesn't seem to be an ecto3 thing at all? |
Actually it looks like someone already has an issue open, from over 2 years ago... >.> Are there any other contributors that are able to update these projects @Stavros that also have hex credentials to push updates? |
@AppyCat would you mind closing this issue? I don't think this is an issue (as titled) any longer. I believe we've already confirmed this together in this other issue: stavro/arc_ecto#104 @bnenu I believe @OvermindDL1 accurately described the issue. Arc simply doesn't support the format of params you're passing in (yet), and there are other issues/PRs open that would help your situation. It's probably best to move the discussion there :) |
Thank you folks for your help! I will be following the discussion on arc_ecto thread, maybe they merge the PR :).Seems that there is a workaround proposed until better days. |
Hi, I'm using Elixir 1.7.3 with Phoenix 1.4.0 with Arc 0.11.0 and Ecto 3.0
Problem is arc_ecto 0.11.0 wants Ecto 2.0
Can arc_ecto work with Ecto 3 on any other branch?
The text was updated successfully, but these errors were encountered: