Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: MBDISCUSSION table
Hi,
I need a question about this table.
I've seen that MBDISCUSSION table is related with MBTHREAD by threadID field, and in turn, MBTHREAD is related with MBMESSAGE by rootMessageId field.
The question i have is that I don´t know what this records are, which one is the representation of this records in the portal. My first thought was that are related with forum post or something like that, but i don´t have any thread or any message in forum in my liferay portal, so, all of the MBMESSAGES that I have do not seem to be posts.
Can anyone tell me what are those tables and which portal process introduces records in those tables?
Kind regards,
Íñigo
I need a question about this table.
I've seen that MBDISCUSSION table is related with MBTHREAD by threadID field, and in turn, MBTHREAD is related with MBMESSAGE by rootMessageId field.
The question i have is that I don´t know what this records are, which one is the representation of this records in the portal. My first thought was that are related with forum post or something like that, but i don´t have any thread or any message in forum in my liferay portal, so, all of the MBMESSAGES that I have do not seem to be posts.
Can anyone tell me what are those tables and which portal process introduces records in those tables?
Kind regards,
Íñigo
Iñigo Boyano
Can anyone tell me what are those tables and which portal process introduces records in those tables?
We'll need a canonical place that states: Hands off the database. It's of no use to understand what's happening in there. You should understand the API, but any database knowledge is actively dangerous: As soon as you assume that you understand it, you're tempted to edit data in it - which might leave data in there that's unexpected by the API. This in turn might break your next upgrade, or result in downtime in 6 months (been there, done that. Seriously).
You can use your time more effectively by looking at anything else but the database.
That being said, MB indeed is for MessageBoard. And the MessageBoard's persistence mechanism is also being used by other features, like comments.
Hi Olaf,
I know that database is UNTOUCHABLE and its for that, liferay provides an API to access and modified their tables.
The question we have is that we have inconsistencies in our DDBB (we thought its due to a problem in a backup). We have 3 items in ASSETENTRY table with the same EntryId.
As far as i know, entryID is primaryKey and we cant have two records in this table with the same id. This problem makes that those entries seem to be corrupt and we cant do anything with their. For example, we have localized an entryId that is a webContent, if we open that content and try to publish another version with some changes, the content don't updated.
The objetive of this post is that one of those duplicated entryid in ASSETENTRY is vincualted to a record of MBDISCUSSION and we want to locate what is this in the portal, the objetive is not to modify by hand the records of DDBB in no case.
Kind Regars,
Íñigo
I know that database is UNTOUCHABLE and its for that, liferay provides an API to access and modified their tables.
The question we have is that we have inconsistencies in our DDBB (we thought its due to a problem in a backup). We have 3 items in ASSETENTRY table with the same EntryId.
As far as i know, entryID is primaryKey and we cant have two records in this table with the same id. This problem makes that those entries seem to be corrupt and we cant do anything with their. For example, we have localized an entryId that is a webContent, if we open that content and try to publish another version with some changes, the content don't updated.
The objetive of this post is that one of those duplicated entryid in ASSETENTRY is vincualted to a record of MBDISCUSSION and we want to locate what is this in the portal, the objetive is not to modify by hand the records of DDBB in no case.
Kind Regars,
Íñigo
Hi Iñigo,
In which version are you working on?
The AssetEntry table has two unique indexes:
Regarding MBDISCUSSION, that is an object which is created anytime you create an object which supports comments, a we content, blog, wiki, etc. You can check the fields classNameId and classPK to reach the associated object. For example, for JournalArticle, the classNameId has to be one assoaciated to JournalArticle and the classPK has to match with the resourcePrimKey in JournalArticle table.
I hope it helps
Cheers!
In which version are you working on?
The AssetEntry table has two unique indexes:
- The one for the PK (EntryId)
- And index IX_1E9D371D on AssetEntry (classNameId, classPK);
Regarding MBDISCUSSION, that is an object which is created anytime you create an object which supports comments, a we content, blog, wiki, etc. You can check the fields classNameId and classPK to reach the associated object. For example, for JournalArticle, the classNameId has to be one assoaciated to JournalArticle and the classPK has to match with the resourcePrimKey in JournalArticle table.
I hope it helps
Cheers!
Getting Issue while Uploading multiple documents to liferay
The table 'MBDiscussion' is full
06:24:53,821 ERROR [http-bio-8080-exec-100][ClpSerializer:770] java.lang.ClassNotFoundException: org.hibernate.exception.GenericJDBCException
java.lang.ClassNotFoundException: org.hibernate.exception.GenericJDBCException
The table 'MBDiscussion' is full
06:24:53,821 ERROR [http-bio-8080-exec-100][ClpSerializer:770] java.lang.ClassNotFoundException: org.hibernate.exception.GenericJDBCException
java.lang.ClassNotFoundException: org.hibernate.exception.GenericJDBCException
Attachments:
ronak vora:
Getting Issue while Uploading multiple documents to liferay
That's an interesting one. I'd rather expect your database to be running out of disk space: There's no reserved space for any particular table.
Copyright © 2025 Liferay, Inc
• Privacy Policy
Powered by Liferay™