Postgrex expected a binary, got %Geo.Point about geo HOT 9 CLOSED

@Virviil I'm not sure either with the information given. It may be a configuration problem. Are the two queries run in the same mix environment? Is there a simpler query you could run that shows it working or not working?

from geo.

Yep, both queries in one session of mix phoenix.server

from geo.

I can provide you any information, just don't know which

from geo.

@Virviil is that the query the Ecto runs? If so could you show me your Ecto query if possible?

from geo.

No problem.

SELECT Request

Repo.all(
    from b in Bookmark,
    where: b.bookmark_type == "public",
    where: st_within(b.latlng, st_buffer(^point, ^radius, 8)),
    where: b.is_active == true and b.is_delete != true,
    order_by: [desc: b.updated_at],
    offset: ^offset,
    limit: ^limit,
    select: b
)

INSERT Request

Just populating changeset, one of the params is %Geo.Point{}, and then Repo.insert

from geo.

@Virviil sorry for the delayed response. I'm not sure what the issue is from looking at it. As far as I can tell from the SQL and from the Ecto query, it all looks correct. It may be a bug here, but not sure. Could also be something with Postgrex, but let's make sure first. What happens if you replace the called to st_within and st_buffer with fragments that call the underlying PostGIS functions?

from geo.

from geo.

Glad you were able to find a workaround. When I have some time I'll try to reproduce this and if I can I'll try to fix it.

from geo.

Going to close this since there was a workaround and nothing has came up since

from geo.