Pull Request for Issue # .

Summary of Changes

This Pull Request changes the joomla.sql files for new installations for both kinds of databases.

MySQL (and MariaDB):

• Code style: Removed redundant spaces and added missing names quoting and a missing line break.
• Fixed alphabetical order of extensions inserted for webservices plugins.

PostgreSQL:

Fix unneeded differences in data between PostgreSQL and MySQL and comments style.

The differences between the databases fixed by this PR are:

• Vote plugin is by default disabled on MySQL, on PostgreSQL it is enabled.
• On MySQL, the default workflow stages and transitions are inserted with the right asset ID's, on PostgreSQL they are inserted with asset ID zero.
• On MySQL, the new record in the extensions table for plg_system_webauthn is inserted with order number zero like it is for all the other extensions, on PostgreSQL it is order number 8.
• The order in which new records for the diverse webservices plugins are inserted into the extensions table differs between the 2 database types.

In the comments for the diverse sections in posgresql/joomla.sql, table names are in most cases quoted like on MySQL, only for a few recently added ones it was done differently. This PR unifies that so a comparison between the two joomla.sql files will not show difference in quotes in these comments.

Finally, fixed alphabetical order of extensions inserted for webservices plugins in the same way as for MySQL.

Testing Instructions

The test consists of 2 parts:

1. Code review.
2. Test if new installation still works.

Instructions for part 1 - code review:

1. Check if the differences shown in the "Files changed" view on GitHub are equal to what is described in the summary of changes above and check that they don't contain any typos or errors.
2. Using a good comparison tool, e.g. BeyondCompare, Araxis Merge, TotalCommander, ..., compare the two joomla.sql files for MySQL and PostgreSQL. Check for all insert statements that they insert the same data and don't contain any differences which are not expected due to the different database type (like e.g. CURRENT_TIMESTAMP being a function or a session variable, that's expected).

Instructions for part 2 - test new installation:

1. Apply the patch of this PR to a current, clean 4.0-dev branch or recent nightly. If necessary remove configuration.php and clear database to prepare a new installation.
2. Make a new installation on whatever kind of database you have available. If you have more than 1, test as many as you feel comfortable with. Verify that the installation works as well as it works without this PR.
3. Login to backend and check it works as well as it works without this PR.
4. When reporting back your test result, please note which kind of database you have tested.

Expected result

After a new installation, the initial data inserted with joomla.sql is the same for MySQL and PostgreSQL databases.

Actual result

After a new installation, the initial data inserted with joomla.sql is different between MySQL and PostgreSQL databases. The differences are as described in the summary of changes.

Documentation Changes Required

None.