掲示板

Database tables for contents and documents/files

12年前 に Radityaputra Rahardjo によって更新されました。

Database tables for contents and documents/files

New Member 投稿: 3 参加年月日: 12/01/11 最新の投稿
Hi guys,

I was wondering, to which table does Liferay portal stores our documents/files and web contents? I need to know because I need to index these files and contents from another web app which is using the Liferay portal repository. And do these tables have a date columns? I need this column to know the last modified date of the files/content. If there isn't a date column, is there any other way to get the last modified date of a file in the database?

Thanks.
thumbnail
12年前 に Juhi Kumari によって更新されました。

RE: Database tables for contents and documents/files

Expert 投稿: 347 参加年月日: 11/12/12 最新の投稿
Hi Radityaputra,

Liferay portal stores documents library files in following tables
dlfileentry,dlfilerank,dlfileshortcut,dlfileversion,dlfolder
and for web contents
journalarticle,journalarticleimage,journalarticleresource,journalcontentsearch,journalfeed,journalstructure,journaltemplate

You can get modified date of web contents in journalarticle,journalfeed,journalstructure,journaltemplate tables
and for Document library file in dlfileentry,dlfileshortcut,dlfolder tables


Regards
Juhi
thumbnail
6年前 に Cesar Ramírez によって更新されました。

RE: Database tables for contents and documents/files

New Member 投稿: 2 参加年月日: 17/08/15 最新の投稿
- Documents library files
DLFileEntry
DLFileRank
DLFileShortcut
DLFileVersion
DLFolder

- Web contents
JournalArticle
JournalArticleImage
JournalArticleResource
JournalContentSearch
JournalFeed
JournalStructure
JournalTemplate
thumbnail
6年前 に Olaf Kock によって更新されました。

RE: Database tables for contents and documents/files

Liferay Legend 投稿: 6403 参加年月日: 08/09/23 最新の投稿
Cesar Ramírez:
- Documents library files
...


This question has been sleeping peacefully since 2012 - are you sure that these match the version that the original question was asked for? And that the content is even in there?

In fact, just these days, there was yet another Database structure discussion. I'm standing by my word there: You shouldn't look at it. At all. Because when you know what's in there, you might be tempted to change it, and that will lead to disaster.

Use the API.