Postgres does not require any extra cycles to support very long text
fields, see the manuals at 8.3. Character Types.
Tip: There are no performance differences between these three types, apart
from increased storage
size when using the blank-padded type, and a few extra cycles to check
the length when storing
into a length-constrained column. While character(n) has performance
advantages in some other
database systems, it has no such advantages in PostgreSQL. In most
situations text or character
varying should be used instead.
This is a feature that I have always (well from 7.x where it was added) and in
general use TEXT for
all of my strings.
Attached is a patch that I have build wrt OfBiz r685532 that adds a new field
type file that is a
copy of the postgresql types except that all of the varchar fields are changed
to text.
I have installed this on a new copy of OfBiz and ran the system in demo/test
and it appears not to
have any problems. The only limit on this is that data dumps from such a system
may not be loadable
on a system running another fieldtype file.
The nature of this change is very simple but if it is necessary for me to file
a copyright assigment
let me know.
--
This email, and any files transmitted with it, is confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email in error,
please advise [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>.
New MDT Software Headquarters (As of July 1, 2008):
3480 Preston Ridge Road
Suite 450
Alpharetta, GA 30005
Philip W. Dalrymple III <[EMAIL PROTECTED]>
MDT Software - The Change Management Company
+1 678 297 1001
Fax +1 678 297 1003
