<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Hierarchy of Filecontentstore in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/hierarchy-of-filecontentstore/m-p/17662#M7974</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Alfresco stores its meta-data about files and nodes in the database. It stores the file content in a nested structure on the filesystem.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It is our belief that it is better to use the most appropriate system for the job, e.g. the database is best for storing structured row-based data, and the filesystem is best for storing lumps of binary data such as file content.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The directory structure used on the filesystem exists to help break up the (potentially huge) number of files in the system into multiple directories. Also the filesystem cannot handle some characters for names of objects that the database can - e.g. the *\/" characters will upset the filesystem if used in a filename etc. where as if we store the meta-data about the files in the database we can use any characters for object names.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 Nov 2005 15:02:37 GMT</pubDate>
    <dc:creator>kevinr</dc:creator>
    <dc:date>2005-11-15T15:02:37Z</dc:date>
    <item>
      <title>Hierarchy of Filecontentstore</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/hierarchy-of-filecontentstore/m-p/17661#M7973</link>
      <description>When I saw the file content store I found that its hierarchy is based on date but not the logical relationship between the contents. Could somebady explain for me why alfresco don't use file system structure to map the logical relationship between the contents? What I mean is to use directory to map</description>
      <pubDate>Mon, 14 Nov 2005 20:32:22 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/hierarchy-of-filecontentstore/m-p/17661#M7973</guid>
      <dc:creator>olive</dc:creator>
      <dc:date>2005-11-14T20:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: Hierarchy of Filecontentstore</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/hierarchy-of-filecontentstore/m-p/17662#M7974</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Alfresco stores its meta-data about files and nodes in the database. It stores the file content in a nested structure on the filesystem.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It is our belief that it is better to use the most appropriate system for the job, e.g. the database is best for storing structured row-based data, and the filesystem is best for storing lumps of binary data such as file content.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The directory structure used on the filesystem exists to help break up the (potentially huge) number of files in the system into multiple directories. Also the filesystem cannot handle some characters for names of objects that the database can - e.g. the *\/" characters will upset the filesystem if used in a filename etc. where as if we store the meta-data about the files in the database we can use any characters for object names.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Kevin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Nov 2005 15:02:37 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/hierarchy-of-filecontentstore/m-p/17662#M7974</guid>
      <dc:creator>kevinr</dc:creator>
      <dc:date>2005-11-15T15:02:37Z</dc:date>
    </item>
  </channel>
</rss>

