- Issue created by @neclimdul
- π³π±Netherlands daffie
Bumping this to major. This is very confusing for site owners. Would be great if we could fix this before Drupal 10.1 is released. Maybe this should even be a "critical" one.
- π·πΊRussia Chi
The issue only applies to MySQL/MariaDB views. Right?
- π¬π§United Kingdom catch
I think it would be reasonable to restrict ::findTables() to only finding actual database tables - we could do that with a change record probably.
I tried to think of bc-friendly options (adding a second argument for $include_views = TRUE? adding a settings override?) but couldn't come up with a use case.
- πΊπΈUnited States neclimdul Houston, TX
I guess this just needs someone to write a patch?
- Status changed to Needs work
over 1 year ago 8:16pm 4 August 2023 - πΊπΈUnited States jrb Raleigh-Durham Area, NC, USA
Here's a patch to get things started. This will:
- Add an optional parameter to findTables() to exclude SQL views from the query.
- Use that parameter in the mysql_requirements() call in mysql.install.
- last update
over 1 year ago Custom Commands Failed - πΊπΈUnited States anoopjohn Washington D. C.
The patch works correctly on a 10.1.6 drupal site and stops showing warnings against views in the database.
- πΊπΈUnited States micahw156
Confirming this patch worked for me on 10.1.6 as well.