Question Kunena 7.1 Beta 3 Released for Joomla! 5.4.x and 6.x

Kunena doesn't register itself in Joomla's #__schemas table by default, so normally System/Maintenance/Database shows nothing for Kunena at all (tested on several environments, including one that's been running for 14 years). So that warning showing up on your site is odd.

Could you check your database's #__schemas table for a leftover/outdated row for com_kunena? If there is one, that's likely the cause - you can just delete it.

For me, the entry has been present in _schemas since Joomla 4, and it has come in handy on a few occasions in the past. After spending the last few days searching in vain for a misspelling that might be causing the database error, I’ve now focused on the system itself and found what I was looking for.
 As a test, I replaced the character ` with the character ´ in the very first line of the file “7.1.0-Alpha1-DEV.sql”.
The error message now read: “The table ‘jom6_kunena_notifications_mailsqueue(‘” does not exist. (From file: “7.1.0-ALPHA1-DEV.sql”.) to a modified message: “The table ‘\“jom6_kunena_notifications_mailsqueue\”’ does not exist. (From file: “7.1.0-ALPHA1-DEV.sql”.)” The single quote was missing.
 The database error appears to lie in this file. I undid the changes and added a space after the top line.
 After that, no further database errors were displayed.
 I then added the space to all test versions and no longer receive any error messages.
  

@Gindi:
If you want to make your own modifications, that's of course up to you. But please don't report bugs here that aren't actual bugs, but the result of your own tinkering. Doing so wastes the valuable time of volunteers who try to help users and reproduce genuine bugs. And this isn't the first time you've come here with a problem you caused yourself.

If you think it would be useful to have Kunena's database tables show up under System/Maintenance/Database, it would be better to open a well-substantiated feature request on GitHub, so the developers can judge whether it makes sense to implement this in a future version.