Replace hardcoded database queries with dynamic queries

I'm having to do the exact same thing on a number of modules but refactors seem to be good 1to1

Love this… I wonder how far would we be from deprecating usage of hardcoded static queries from non-test, non-database core code. +1

Not sure if there is a page somewhere but would be cool to see the all sql queries keywords with their dyanmic counterparts

#6 well the Database API documentation and https://www.drupal.org/docs/8/api/database-api/dynamic-queries → in particular covers that pretty well already, IMO

OK I was expecting a big MR, but this is actually very minimal.

Not 100% sure about dblog though, wouldn't it make more sense to provide mongodb_log since I would imagine the stored format of the messages could then be optimised?

@catch: We have changed a lot of hardcoded SQL queries to dynamic queries in the past. If you want, I will go and search for those issues. These are the hardcoded queries that are left. The remaining ones are mostly in Drupal's critical path.
I am at the moment still in the phase of getting Drupal on MongoDB to support all the features. Drupal on MongoDB now is at a 99% pass rate for the CI pipeline 📌 Drupal on MongoDB (the full PR) Active . Sooner or later I will get the phase where MongoDB specific improvements will be added. I am still not at the point where I have an official go for Drupal on MongoDB from the Drupal Core committer team. :)

We have changed a lot of hardcoded SQL queries to dynamic queries in the past.

Yes I remember that, I just though it would be worse than this even with those issues having landed already ;) Remaining ones are in database cache backend etc.

Even though I'm not sure dblog-on-mongodb makes sense in practice, it doesn't hurt to make it work. Committed/pushed to 11.x, thanks!

catch → closed merge request !9540

Automatically closed - issue fixed for 2 weeks with no activity.