#__content or #__ucm_content

[Roger at Gmail]

Hi
I’m writing a component which needs to access display and update information about articles.

Previously (a long long time ago) there was a simple table #__content which contained all the article info. But now there is also another table #__ucm_content which seems to duplicate much of #__content although not all rows in #_content have a corresponding row in #__ucm_content.

In my example case #__content currently has 202 rows (192 published) and #__ucm_content has 82 so clearly the ucm one is not the primary one.

My question is what on earth is this newer table #__ucm_content for?
Why does it exist?
If I update content in #__content (eg changing the body, or a category or a date do I also have to update the corresponding row in #__ucm_content if it exists?
Does it matter if they get out of sync?
What causes the ucm entries to exist - how come only about half my articles seem to have a ucm entry?

This smells like really poor db design.

If I assign a new tag to an article do I also need to update the column in #__contentitem_tag_map that links to #__ucm_content? I had assumed I could simply add or delete rows in the map table to link content to tags but perhaps its not that simple?

If I want to add or delete a tag for an article can I simply insert or delete a row in the map table and ignore the ucm table?

I cannot find any meaningful documentation about this searching the documentation website - if there is some I apologise for being unable to find and and being made to appear stupid - please could someone post a link to it.

Any advice please?

Many thanks
Confused of Cornwall (RogerCO)

[Hannes Papenberg]

That table is crap and will be gone in 4.0. concentrate on #__content.

Am Mi., 16. Jan. 2019, 18:05 hat 'Roger at Gmail' via Joomla! General Development <joomla-de...@googlegroups.com> geschrieben:

--
You received this message because you are subscribed to the Google Groups "Joomla! General Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-gene...@googlegroups.com.
To post to this group, send an email to joomla-de...@googlegroups.com.
Visit this group at https://groups.google.com/group/joomla-dev-general.
For more options, visit https://groups.google.com/d/optout.

[Roger at Gmail]

Thank you Hannes - your 4th word was how it seemed to me. I’m just slightly worried that something must be using it as rows are getting created for recent articles and if I ignore it will something else stop working…? (I’ll have sites in J3 for a good long while yet I suspect)