Log Message:
-----------
From: Bort, Paul
Subject: RE: Patch for Dia templates for Postgresql_AutoDoc
Date: Tue, 22 Jun 2004 15:23:24 -0400
I've used the same method of shortening as the constraint you mentioned, but
I made it a new entry (table_comment_dia) in the hash rather than mangle the
existing one. I tried to follow the existing naming conventions and coding
style. I picked a total of 45 characters because that seems to be about the
right size on my screen. In testing I also found a bug in Dia that causes a
crash if a comment is too long, but that seems to be in the 100+ character
range, so I'm not worried about 45.
Here are the patches for postgresql_autodoc.pl, dia.tmpl, and
zigzag.dia.tmpl.
Modified Files:
--------------
autodoc:
dia.tmpl (r1.1.1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/dia.tmpl.diff?r1=1.1.1.1&r2=1.2)
postgresql_autodoc.pl (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/postgresql_autodoc.pl.diff?r1=1.3&r2=1.4)
zigzag.dia.tmpl (r1.1.1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/zigzag.dia.tmpl.diff?r1=1.1.1.1&r2=1.2)
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
