Author's note: I originally published this on October 19th. I then grew dissatisfied and wrote a post v2. This is perhaps the reason I failed Engl

Moosieus' Things n' Stuff

submited by

Style Pass

2024-10-21 22:30:04

Author's note: I originally published this on October 19th. I then grew dissatisfied and wrote a post v2. This is perhaps the reason I failed English courses and became a software engineer.

ParadeDB is an alternative to ElasticSearch built on Postgres. More technically, it's a trio of extensions that fulfill the same purpose:

ParadeDB 0.11.0 dropped last week with lots of improvements, including an overhauled API. The syntax is far more viable for database access layers (DBALs) to accommodate.

In my prior attempt to support ParadeDB in Elixir, I had to completely fork Ecto to support search query composition. This is because previous versions of ParadeDB embedded search queries entirely in the FROM expression like so:

Search queries had a very visible start with call_search_idx.search( and ending at ). This simplified parsing and planning but posed several downsides:

With this new API, ParadeDB's much more involved with query planning and execution, and DBALs have an easier go of things: