<?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 Use 'text' instead of 'varchar' in PostgreSQL 9.x in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/use-text-instead-of-varchar-in-postgresql-9-x/m-p/238861#M191991</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;According to PostgreSQL mail developers, you can exchange all "varchar(…)" by text with advantages only (if should work even faster, because PostgreSQL doesn't need to enforce size).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Reference: &lt;/SPAN&gt;&lt;A href="https://www.postgresql.org/docs/9.1/static/datatype-character.html" rel="nofollow noopener noreferrer"&gt;https://www.postgresql.org/docs/9.1/static/datatype-character.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Tip: There is no performance difference among these three types, apart from increased storage space when using the blank-padded type, and a few extra CPU cycles to check the length when storing into a length-constrained column. While character(n) has performance advantages in some other database systems, there is no such advantage in PostgreSQL; in fact character(n) is usually the slowest of the three because of its additional storage costs. In most situations text or character varying should be used instead.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm running Activiti 5.20.0 with "text" instead "varchar", and have found no error so far.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Edson Richter&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 04 Jun 2016 20:56:54 GMT</pubDate>
    <dc:creator>edsonrichter</dc:creator>
    <dc:date>2016-06-04T20:56:54Z</dc:date>
    <item>
      <title>Use 'text' instead of 'varchar' in PostgreSQL 9.x</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/use-text-instead-of-varchar-in-postgresql-9-x/m-p/238861#M191991</link>
      <description>According to PostgreSQL mail developers, you can exchange all "varchar(…)" by text with advantages only (if should work even faster, because PostgreSQL doesn't need to enforce size).Reference: https://www.postgresql.org/docs/9.1/static/datatype-character.htmlTip: There is no performance difference a</description>
      <pubDate>Sat, 04 Jun 2016 20:56:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/use-text-instead-of-varchar-in-postgresql-9-x/m-p/238861#M191991</guid>
      <dc:creator>edsonrichter</dc:creator>
      <dc:date>2016-06-04T20:56:54Z</dc:date>
    </item>
    <item>
      <title>Re: Use 'text' instead of 'varchar' in PostgreSQL 9.x</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/use-text-instead-of-varchar-in-postgresql-9-x/m-p/238862#M191992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks Edson,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;As I read in the link you provided It seems it is a good idea to change it, but before changing it we should make sure there are no other side effects in the context of this application.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for the hint.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Jun 2016 06:04:27 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/use-text-instead-of-varchar-in-postgresql-9-x/m-p/238862#M191992</guid>
      <dc:creator>vasile_dirla</dc:creator>
      <dc:date>2016-06-06T06:04:27Z</dc:date>
    </item>
  </channel>
</rss>

