History has shown that people tend to change the database if they
assume they understand it. Save yourself from that hassle. Liferay has
internal structures and exposes their API - don't look at the
persistence out of interest. Rather invest valuable brain cycles into
understanding what's actually usable.
What is the role of XXX table? Simple: It stores data. That's the
amount of knowledge required.
What happens if table XXX is not there? Some persistence will fail
and you'll have a broken installation. Again: That's what you need to know
What happens if you cause any of expected tables OR RECORDS to not be
there? Or to be there though not expected? Or to have different data
than expected? Your installation will be broken.
Want a fast path to a broken system? Mess with the database! The
first step there is trying to understand how a particular entity is
stored. The storage is not guaranteed to be stable,
and it's not documented as there's no assumption that it
doesn't change with the next minor release. Any such change
might break your system even if you happened to
understand today's use of those tables correctly and completely. Which
you probably won't.
