I'm pretty sure these types are just not compatible? One is stored as a string and the other is stored as an array, so you can't compare them in postgres. I don't think there is anything we can do to fix it. storage_type on StringPoint is :string.

I've removed the commits from the main branch but there is a branch with your failing tests in point-test. I don't think that its possible to compare these disparate types at the data layer.

I'm not sure I understand. I'm not trying to compare between attributes of different types but of the same type (Point with Point and StringPoint with StringPoint). Maybe I should separate into 2 tests?

From my understanding the error is happening when joining across tables and the join key coming from elixir side is not being properly casted/encoded in the query. For example, StringPoint is represented as a struct on elixir side and should be saved/encoded as a string in postgres. In this case, it should be encoded (dump_native) before being used in the join condition, but it is not hence the error:

* ** (DBConnection.EncodeError) Postgrex expected a binary, got %AshPostgres.Test.StringPoint{x: 2.0, y: 3.0, z: 4.0}. Please make sure the value you are passing matches the definition in your table or in your query or convert the value accordingly.

Ah, okay, apologies for the confusion :)

Can you open an issue and reference this PR? I will re-add the tests and investigate 🙇

I've found the issue, will work on a fix 😄

@quartz55 might be worth confirming actually: in your real issue, is the value that you are using a tuple? i.e {1, 2, 3}? Or is it some other value? Because this issue is actually in our filter parsing in Ash core and only arises when you use tuples for relationship keys or primary keys.

Looks like there is another issue, which is that (from what I can tell) ANY only supports scalar values.

Okay, there were three separate bugs related to tuple values and multidimensional array values here. They are fixed now in ash_sql and ash main, and will be released next week.

@quartz55 might be worth confirming actually: in your real issue, is the value that you are using a tuple? i.e {1, 2, 3}? Or is it some other value? Because this issue is actually in our filter parsing in Ash core and only arises when you use tuples for relationship keys or primary keys.

My real issue is more or less replicated by the StringPoint type not the tuple one. Specifically I'm using country codes in the database as natural keys string type (e.g. PT or US) but in Elixir land they are decoded as a struct (defstruct [:code, :name, flag: nil]). I seem to have issues when this type is used as a join/relationship key because they are not encoded back to a string in SQL queries (it fails here in the test).

Does it still fail after the recent fixes?

Pointing both to main (ash and ash_sql) seems to have fixed it indeed! 🙌