topic Re: content url from database in Alfresco Archive

content url from database

skorde — Thu, 28 Jan 2010 11:22:11 GMT

HiI would like to know the easiest way to get the content url of the document stored in alfresco enterprise 3.2. I have document name and I want to know exact file system location of documents stored in alfresco server.In Alfresco 2.1 we where get this url from alf_node_properties table.Could you pl

Re: content url from database

derek — Thu, 28 Jan 2010 12:35:51 GMT

Hi,
The Node property now stores a long_value, which is the ID of a row in the alf_content_data table that references the alf_content_url table.


        select
            np.long_value as id
        from
            alf_node_properties np
        where
            np.node_id = ? and
            np.qname_id = ? and
            np.actual_type_n = 3 and
            np.persisted_type_n = 3
‍‍‍‍‍‍‍‍‍‍‍

Regards

Re: content url from database

luca — Tue, 19 Oct 2010 09:02:11 GMT

Hi,
I just upgraded from Alfresco 3.0 to 3.2. Now when I upload a document in Alfresco the contentUrl is written in this new table alf_content_url.

I have only a question. :?:
Why the old documents have their contentUrl in alf_node_properties and the upgrade process didn't migrate them in alf_content_url?

Thanks in advance.

Re: content url from database

derek — Fri, 22 Oct 2010 21:50:06 GMT

Hi,
… because the original intention was to avoid a long-running patch. Unfortunately, some other bugs mean that we had to eventually migrate the data over. See ALF-726. So you'll want to disable the cleaner and plan for an upgrade to 3.4 to get the full fix.

Re: content url from database

luca — Mon, 25 Oct 2010 08:12:29 GMT

ALF-726 bug is introduced in 3.2.r, as they say.

I'm using Alfresco 3.2, should I disable ContentCleaner anyway?

Re: content url from database

derek — Mon, 25 Oct 2010 11:14:59 GMT

It was disabled for 3.2 Community (check for bean fileContentStoreCleanerJobDetail in WEB-INF/classes/alfresco/scheduled-jobs-context.xml). It is re-enabled in 3.3 Community with the appropriate patches to fix it all up.