Service not found exception

When upgrading the sqlsrv module to a version higher than 4.3.0 (i.e 4.3.1), sqlsrv.views.date_sql in sqlsrv.services.yml is set to private which means it cannot be accessed directly from the container at runtime. I changed the value in the public parameter from 'false' to 'true' in sqlsrv.services.yml and was able to fix the error. I attached a patch with the fix.

@Beakerboy is correct in #4 🐛 Service not found exception Fixed , in that the intended approach for backend overridable services is that you would ask for the overridable service from the container (views.date_sql in this case) and you would get the correct backend version of the service corresponding to the preferred default backend configured in your site's services.yml, e.g.

parameters:
  default_backend: sqlsrv

This is presumably why the core backend implementations are marked private - they're only intended to ever be used via the backend override mechanism rather than injected directly at runtime. However this doesn't take into account use cases where the database driver is used to access a secondary database, where defining the default_backend in that way is not applicable (if the primary database is Mysql then the default backend still needs to be mysql).

Allowing the sqlsrv.views.date_sql to be public is therefore necessary to facilitate these kinds of use cases, so Maather's patch in #6 🐛 Service not found exception Fixed is the correct fix.

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