[WIP] Ecto 2 compatibility #84
Conversation
|
Hey Michal, any news about this upgrade? I'm trying to use scrivener_ecto package but it requires Ecto 2.0. Thanks! |
|
@michalmuskala is this still in the works? I don't know how much work is involved to finish this but I would be happy to kick in $200 if it helps. Looks like there are a few people wanting this so maybe we could setup something like patreon? |
|
+1 |
fix update_all and insert_all tests
|
For anyone that is waiting for this. Please look at #91. I am actively working on it. |
* Mongo does not support returning * Mongo does not support joins * Mongo does not support composite keys
Mongo wants you to be explicit about not wanting the ID field returned
Fix ecto migrate
Fix logging
[WIP] Support for Ecto 2.0
|
Hello, stupid question, but when do you think it's going to be fixed? Regards, |
|
@rsilvestre This is already in a good place. Myself and others are already using it in production. All you need to do is point your dependency to this repo and branch. Something along the lines of {:mongodb_ecto, github: "michalmuskala/mongodb_ecto", branch: "ecto-2"}That should get you started. I believe the reason there has not been an actual release yet is because we are still touching up documentation, and there are a couple fixes that need to be applied to |
|
Hi @ankhers is there a list of fixes which we're waiting on to be applied to Ecto? |
|
@johnnyshields Unfortunately I do not have that list. @michalmuskala would have a better idea of the changes that are required. |
* Fix pattern matching error when creating uniqueness index * Ensure returning the expected tuple for uniqueness validations * Remove unnecessary string interpolation
* updated travis.yml * requires Elixir ~> 1.2 * restored recipients
|
I am going to close this in favour of the 2.1 branch release. |
This updates driver to the new db_connection based version and ecto to 2.0.