Code Excursion

Database Changes After Adding Service Component

What data changes occur when adding a service component in Liferay. Also included system level configuration. This information was added by administrator user Test Test with email test@test.com. Keep in mind that Liferay doesn’t enforce referential integrity in the database. Instead it is “enforced” in the code.

The following table was modified but appears not to be strongly relevant.

• DispatchLog
• PortletPreferences
• QUARTZ_TRIGGERS
• User_
• ViewCountEntry

The following table was modified. It appears that a record was created each time the service component was deployed. The system level configuration did not appear to have a database component.

• ServiceComponent
  • 15 records inserted.
  • Primary key is serviceComponentId.
  • Excerpt of inserted records

    • serviceComponentId	buildNamespace	buildNumber
      33554	com.acme.y7g4.service	4
      33553	com.acme.y7g4.service	3
      33550	com.acme.y7g4.service	2
      33549	com.acme.y7g4.service	1

  • data_ column contains xml that details table to be added to database.

XML from Data_ column

<?xml version="1.0"?>

<data>
	<tables-sql><![CDATA[create table FOO_Foo (
	uuid_ VARCHAR(75) null,
	fooId LONG not null primary key,
	groupId LONG,
	companyId LONG,
	userId LONG,
	userName VARCHAR(75) null,
	createDate DATE null,
	modifiedDate DATE null,
	field1 VARCHAR(75) null,
	field2 BOOLEAN,
	field3 INTEGER,
	field4 DATE null,
	field5 VARCHAR(75) null
);]]></tables-sql>
	<sequences-sql><![CDATA[]]></sequences-sql>
	<indexes-sql><![CDATA[create index IX_CFFD06FF on FOO_Foo (field2);
create unique index IX_905CD589 on FOO_Foo (uuid_[$COLUMN_LENGTH:75$], groupId);]]></indexes-sql>
</data>

Diagram is only showing the relationships most relevant.

Resources

• Before Database Dump
• After Database Dump
• PlantUML Changed Data Diagram