Database level changes in Quarterly Releases
Written By
Rishabh Agrawal
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- What are the database-level changes from DXP 2023 Q4.0 to DXP 2024 Q2.0?
- Are there any additions of new tables, fields, and modifications to the existing tables?
Environment
- Liferay DXP [all versions]
Resolution
- The Liferay database is the product database. Liferay DXP needs the database to be structured in the way it's delivered/upgraded so that no one should change the structure at all.
- When using Liferay, the database should be considered a black box that must not be changed outside of API usage. It is an integral part of the product.
- Making manual changes in a Liferay database violates support guidelines and prevents Liferay Support from assisting with issues caused by doing so.
- Liferay provides a comprehensive API that can be used to interact with all the content that is stored in the database.
- The only way users should insert or manipulate data should be the API.
- No component in Liferay itself (apart from the actual persistence layer) manipulates the database directly: Everything utilizes the API.
Did this article resolve your issue ?