Ecto.Changeset.no_assoc_constraint/3 does not work

Test environment:

Erlang/OTP 25 [erts-13.1.2] 
Elixir 1.14.2 
ecto 3.10.3
ecto_sql 3.10.1
ecto_sqlite3 0.10.3

Description:
Suppose it, as a completely straightforward use case, as the documentation of no_assoc_constraint/3 expressed (and the same code is working fine on postgrex).

P.S. As I am reporting this, I see there are two other releases come out and sounds like non of them addressed this issue, so I didn't check them.

sounds like non of them addressed this issue, so I didn't check them.

That is correct, none of them address this. We'll need to add unit tests for this and figure out why it was missed. This was a feature added 8 years ago to ecto.

Looks like a test would have covered this but we ignore it because we can't get nicely formatted FK errors

ecto_sqlite3/integration_test/test_helper.exs

Lines 85 to 88 in 37b68d9

    
           # sqlite supports FKs, but does not return sufficient data 
        
           # for ecto to support matching on a given constraint violation name 
        
           # which is what most of the tests validate 
        
           :foreign_key_constraint,

	# sqlite supports FKs, but does not return sufficient data
	# for ecto to support matching on a given constraint violation name
	# which is what most of the tests validate
	:foreign_key_constraint,