After some experimentation and some RTFM-ing I realized that of course I wanted 'bytea' fields instead of 'text' fields.

Currently we use a Documents table with a bunch of information in it as part of our system; including the file itself would smooth a lot of things out -- we'd have to copy the file from Postgres to the file system for processing but (this is the cool part that I love) any files that were created during processing can then be stored back into the database. This means that we have the ability to back-track to previous iterations. (For obvious reasons, I can't describe my system in a lot of detail.)

Your advice (third paragraph) does make sense .. thanks for the pointers. I'll be reading up on SPOPS more this week to see if we can fit your wheel in somewhere rather than build our own.

--t. alex
Life is short: get busy!

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.