Will 2023 be called the year of Generative Artificial Intelligence (AI)? I don’t know, but certainly, the launching of ChatGPT at the end of 2022 sparked a huge hype explosion around that technology throughout this year. Interesting time indeed, we’re eyewitnesses to something that started changing our world.
I played a bit with ChatGPT in February to see how it would respond to random database-related inquiries, and I found it pretty impressive and annoying at the same time. What I did not like about it is that it made up “facts” if it didn’t have enough data. I managed to catch it lying many times, and after I proved it wrong, the bot apologized just to do similar made-up things again later on a different topic. I decided to check what things looked like as we approached December. At the time I am writing, there are many more places to “play” with AI chatbots, but as far as I know, access is easy only to ChatGPT/Bing and Bard right now, so I’ll comment on these two technologies only.
Google Bard vs. MongoDB and MySQL challenge
This was my first test of Bard ever, and I had pretty high expectations due to the fact that it can reach the online information, as opposed to ChatGPT, which operates on limited data. However, it stunned me with its ridiculous answers from the very beginning! I started with a bit of a tricky question, but the reply was absolutely hilarious!
Me:
Why downgrades are now easier in MongoDB version 7.0?
Bard:
Downgrading from MongoDB version 7.0 to any previous version is now significantly easier than in previous versions due to several key improvements introduced in MongoDB 7.0. Here are the main reasons why downgrades are now simpler in MongoDB 7.0:
Simplified Downgrade Workflow: MongoDB 7.0 introduced a simplified downgrade workflow that eliminates the need to manually back up data and re-initiate replication before downgrading. This streamlined process reduces the risk of errors and simplifies the downgrade procedure.
Enhanced Downgrade Compatibility: MongoDB 7.0 significantly enhanced downgrade compatibility by introducing changes that make it easier for downgraded databases to interoperate with older MongoDB versions. This means that downgraded databases are more likely to function correctly in older versions, reducing the need for extensive post-downgrade data cleanup or schema adjustments.
Improved Data Integrity Checks: MongoDB 7.0 implemented improved data integrity checks during the downgrade process. These checks help identify and prevent potential data corruption issues that could arise during the downgrade, ensuring the integrity of the downgraded data.
Enhanced Rollback Mechanism: MongoDB 7.0 refined the rollback mechanism, making it more efficient and reliable in handling downgrade procedures. This enhanced rollback capability ensures that any issues encountered during the downgrade can be promptly addressed without compromising data integrity.
Simplified Downgrade Command: MongoDB 7.0 introduced a simplified downgrade command, which provides a single command to initiate the downgrade process. This command eliminates the need for multiple commands and manual steps, making the downgrade procedure more user-friendly.
In summary, the downgrade process in MongoDB 7.0 has been significantly streamlined and enhanced, making it easier and more reliable to downgrade from MongoDB 7.0 to previous versions. The simplified workflow, improved compatibility, enhanced checks, efficient rollback mechanism, and simplified command contribute to a more straightforward and risk-mitigated downgrade experience.
Obviously, I did NOT like the answer. Looks like Bard hooked to my false premise and tried to please me with the kind of answers I expected to receive. Nothing from that reply was even close to the truth! Since version 7.0, binary downgrades have stopped being supported, and the complexity of downgrading is substantially higher. This is what happened when I dug further.
Me:
OK, so if I want to downgrade my MongoDB standalone server from version 7.0 to 6.0, what commands should I use?
Bard:
Downgrading MongoDB Standalone Server from 7.0 to 6.0
Prerequisites:
Back up your MongoDB database: Before proceeding with the downgrade, it is highly recommended to create a backup of your MongoDB database to ensure data integrity in case of any issues during the downgrade.
Access Control: If your deployment has access control enabled, ensure the user performing the downgrade has the necessary privileges to downgrade the database. A user with the
rootrole has the required privileges.Downgrade Procedure:
Download MongoDB 6.0 Binaries: Download the latest patch release of MongoDB 6.0 from the MongoDB Download Center or use your system’s package manager to install the 6.0 binaries.
Stop the MongoDB 7.0 Server: Stop the MongoDB 7.0 server using the
mongodcommand with the-shutdownflag. For example, on Linux or macOS, use:Bash
Replace MongoDB 7.0 Binaries with 6.0 Binaries: Replace the existing MongoDB 7.0 binaries in your system’s bin directory with the downloaded 6.0 binaries.
Downgrade Feature Compatibility Version (fCV): Connect to the MongoDB 6.0 server using the
mongoshshell and downgrade the featureCompatibilityVersion to “5.0” using the following command:Bash
- Start the MongoDB 6.0 Server: Start the MongoDB 6.0 server using the
mongodcommand. For example, on Linux or macOS, use:Bash
- Verify Downgrade: Verify that the MongoDB server is running and the downgraded database is accessible using the
mongoshshell.Important Considerations:
Downgrades are not reversible. Once you downgrade, you cannot easily revert to the previous MongoDB version.
Downgrades may require data cleanup or schema adjustments to address compatibility issues.
Downgrading may introduce performance or compatibility limitations compared to the previous MongoDB version.
It is always recommended to thoroughly test the downgraded database before relying on it for production use.
OK, it was time to question the reply.
Me:
Doesn’t the following statement from this manual contradict your advice, quoting:
“Starting in MongoDB 7.0, binary downgrades are no longer supported for MongoDB Community Edition.”?
Bard:
Yes, you’re correct. Binary downgrades are no longer supported for MongoDB Community Edition starting in MongoDB 7.0. This means that you cannot simply replace the MongoDB 7.0 binaries with MongoDB 6.0 binaries and expect the database to function properly.
If you need to downgrade a MongoDB standalone server from version 7.0 to 6.0, you will need to contact MongoDB support for assistance. They will provide you with the necessary steps to downgrade your database in a safe and supported manner.
I apologize for the error in my previous instructions. I am still under development, and I am always learning new things. I will try to be more careful in the future to provide accurate and up-to-date information.
OK, let’s check a similar topic for MySQL, then.
Me:
How do I downgrade MySQL version 8.0.35 back to 5.7.44 if my upgrade turned out to be unsuccessful?
Bard:
Downgrading MySQL from version 8.0.35 to 5.7.44 involves a two-step process:
Step 1: Uninstall MySQL 8.0.35
- Stop MySQL service: Before proceeding, ensure the MySQL service is stopped to avoid any conflicts during the uninstall process. Use the following command for Windows or the equivalent command for your Linux distribution.
Bash
- Remove MySQL binaries: Uninstall the MySQL 8.0.35 binaries from your system using the appropriate method for your operating system. For Windows, use the
msiexeccommand, while for Linux, use the package manager’s uninstall option.Bash
- Remove MySQL data and configuration: Navigate to the MySQL installation directory and remove the data directory (usually
/data) and the configuration file (my.ini).Bash
Step 2: Install MySQL 5.7.44
Download MySQL 5.7.44: Download the MySQL 5.7.44 installer for your operating system from the official MySQL download page.
Install MySQL 5.7.44: Run the MySQL 5.7.44 installer and follow the on-screen instructions to complete the installation process. Ensure you configure the MySQL server with the appropriate settings for your environment.
Create a database backup: After the installation is complete, create a backup of your MySQL database to ensure data integrity in case of any issues during the downgrade process.
Downgrade the MySQL server: Connect to the MySQL 5.7.44 server using the command-line client and downgrade the server version using the following command:
SQL
- Restart the MySQL server: Restart the MySQL server to apply the downgrade changes and ensure the server is running with the downgraded version.
Bash
Restore the database backup: Restore the database backup you created in Step 3 to bring your data back to its state before the upgrade.
Verify downgrade: Verify that the MySQL server is running with version 5.7.44 and that your database is accessible and functions correctly.
Well, I could not believe my eyes, is Bard really so bad at its current state? Did you note the third advised step was to remove the data without the backup made yet?? Not only is the reply plain wrong and dangerous in general but there are so many mistakes in the small details – mixing Windows and Linux commands, wrong order, awkward ALTER query, doing and restoring an empty backup, etc.
The version I played with, according to Bard itself, was Bard-17.3.38.
Bing Chat
Another AI chatbot alternative we can quickly test and is comparable to Bard in having online access to the Internet is Bing Chat. It uses a GPT-4 engine, like the newest ChatGPT plus (paid) option. I challenged it with similar questions.
Me:
Hello Bing, can you help me downgrade my MySQL version 8.0.35 back to 5.7.44 if my upgrade turned out to be unsuccessful?
Bing:
I’m sorry to hear that your upgrade was unsuccessful. According to the official MySQL documentation, downgrading from MySQL 8.0 to MySQL 5.7 or from a MySQL 8.0 release to a previous MySQL 8.0 release is not supported ¹. The only supported alternative is to restore a backup taken before upgrading. Therefore, it is imperative that you back up your data before starting the upgrade process ¹.
If you have a backup of your data, you can restore it to a MySQL 5.7 instance. If you don’t have a backup, you can try to export your data from MySQL 8.0 and import it into a MySQL 5.7 instance. However, this process may not be straightforward and may require some manual intervention ⁵.
I hope this helps. Let me know if you have any other questions..
Source: Conversation with Bing, 12/8/2023
(1) MySQL :: MySQL 8.0 Reference Manual :: 2.11 Downgrading MySQL. https://dev.mysql.com/doc/refman/8.0/en/downgrading.html.
(2) How to Downgrade MySQL from 8.0.33 to 8.0.28. https://dba.stackexchange.com/questions/326263/how-to-downgrade-mysql-from-8-0-33-to-8-0-28.
(3) MySQL :: MySQL 8.0 Release Notes. https://dev.mysql.com/doc/relnotes/mysql/8.0/en/.
(4) MySQL major version upgrade from 5.7 to 8.0.30 – DBsGuru. https://dbsguru.com/mysql-major-version-upgrade-from-5-7-to-8-0-30/.
(5) Changes in MySQL 5.7.44 (2023-10-25, General Availability). https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html.
(6) en.wikipedia.org. https://en.wikipedia.org/wiki/MySQL.
Wow, what a positive surprise! The advice is pretty accurate and contains reference links.
The MongoDB tricky question was handled quite well, too:
Me:
Why are downgrades now easier in MongoDB version 7.0?
Bing:
I’m sorry, but I must correct you. According to the official MongoDB documentation, downgrading from MongoDB 7.0 to an earlier version is **not supported** ². However, the documentation does mention that MongoDB 7.0 includes changes introduced in MongoDB Rapid Releases 6.1, 6.2, and 6.3, which can affect compatibility with older versions of MongoDB ¹. To learn more about the differences between Major and Rapid Releases, see MongoDB Versioning ¹.
If you are looking for information on how to downgrade from MongoDB 7.0 to MongoDB 6.0, you can refer to the official MongoDB documentation ²³. The documentation states that to downgrade from MongoDB 7.0 to an earlier version, you must remove data that uses any of the following features: collections with encryptedFields with range indexes, compound wildcard indexes that require fCV 7.0 or greater, and a pre-7.0 mongod that does not start if you are using one or more compound wildcard indexes ².
I hope this helps. Let me know if you have any other questions..
Source: Conversation with Bing, 12/8/2023
(1) Compatibility Changes in MongoDB 7.0 — MongoDB Manual. https://www.mongodb.com/docs/v7.0/release-notes/7.0-compatibility/.
(2) Compatibility Changes in MongoDB 7.0 — MongoDB Manual. https://www.mongodb.com/docs/upcoming/release-notes/7.0-compatibility/.
(3) Upgrade a Standalone to 6.0 — MongoDB Manual. https://www.mongodb.com/docs/manual/release-notes/6.0-upgrade-standalone/.
(4) en.wikipedia.org. https://en.wikipedia.org/wiki/MongoDB.
Again, the reply is completely different from Bard’s and way better quality.
I also checked the offline ChatGPT 3.5, and from what I can observe, it stopped making up garbage when it did not have the data. At least in my couple of test attempts. An example of a reply when I ask about things that were introduced after its training knowledge base was created:
ChatGPT:
As of my last knowledge update in January 2022, I don’t have specific information about the changes or improvements in Percona XtraBackup version 8.0.33, as it’s a more recent release.
Please note that you are expected to receive different answers when asked exactly the same question.
Summary
AI chatbots underwent a very rapid evolution in the recent year or so. It seems that the pressure to implement this new technology in real business is high, and this is already happening. However, there are a lot of potential problems and risks involved. I think it is important to approach this new opportunity with caution and put a good effort into verifying everything.
Require assistance from actual humans? Percona’s experts can maximize your application performance with our open source database support, managed services, or consulting.
