This is a list of issues found with Ecto (Elixir).
Note that most of these are not required to get Ecto working, but each of these can be a potential roadblock when migrating an existing app to cockroach.
I believe support for the timestamp precision has been reverted.
Discussion at https://github.com/cockroachdb/cockroach/issues/32098#issuecomment-594545673.
@DavidOliver this will be in 20.1 and you can see it in this beta (https://www.cockroachlabs.com/docs/releases/v20.1.0-beta.2.html)
Note that #24897 is resolved.
Not possible to change stored query on a view, must drop the view and recreate #24897
32917 Must do foreign keys in three separate migrations (add column, add an index on that column, add the constraint)
Zendesk ticket #5257 has been linked to this issue.
note that named SAVEPOINT support will also be included in 20.1
It should be noted that with CDB 20.1 all the major issues have been fixed but one as soon as you are running tests. This is fixed on master but it has yet to be released.
Additionally:
if_not_exists / if_exists is missing for now (https://github.com/elixir-ecto/ecto_sql/issues/247)Thanks for filing those two new issues!
I found a problem when creating schemas with Ecto.Migration.
This code just hangs after the execution and the next migration never runs. I'm testing on 20.2
defmodule ProcessosApi.Repo.Migrations.CreateMySchema do
use Ecto.Migration
def change do
execute "CREATE SCHEMA myschema"
end
end
I don't know if this is the correct place to report this. If not just lemme know and I'll move to the correct place.
Thanks in advance!
Most helpful comment
@DavidOliver this will be in 20.1 and you can see it in this beta (https://www.cockroachlabs.com/docs/releases/v20.1.0-beta.2.html)