If you are using #CrunchyBridge managed Postgres, here is a quick video on how query performance can be accelerated and network latency reduced. You can add PolyScale to your Crunchy architecture in a few minutes, without writing code or deploying servers.

https://youtu.be/GNqBogLOjo4
#postgresql #postgres #caching

As an update to this, the developer has been amazing and gave me a patch within hours and #CrunchyBridge have offered to apply it to my database so I can check it works.

I’m so impressed and grateful to both.

My adventures into #MongoDB via #Postgres nearly ground to a halt since boolean query expressions were not fully supported until a recent version (https://github.com/EnterpriseDB/mongo_fdw/issues/58#issuecomment-1569464315 ) which I don’t think #CrunchyBridge are use yet but then #Ecto query fragments (https://hexdocs.pm/ecto/Ecto.Query.html#module-fragments) came to the rescue.

In Postgres, “WHERE ‘active’ = false” doesn’t work but “WHERE ‘active’ is false” does but Ecto’s queries become the former.

My fragment is:

“where: fragment(“? Is false”, d.active)”

#MyElixirStatus

TodayI’ve been getting the #MongoDB foreign data wrapper set up in my #CrunchyBridge database. This is to eventually ease our migration from our current platform to our new one but right now it will allow us to add some brand new functionality to the new platform whilst using our current database seamlessly. For example, we are building a corporate billing module in the new platform which can now easily access the data it needs.

Some info about the FDR is at https://www.crunchydata.com/blog/easy-mongo-from-your-postgres