btw, latin1 may be a more suitable choice than ascii.
Reviewing my notes from a year ago, there were a few cases where ; was not quoted in values, causing premature EOLs, for example:
ERROR: unterminated quoted string at or near "'2m035 1/15hp universal 115volt 2 1/4 x 2 3/4 x4 1/4 ;" at character 993427
and other control codes in inappropriate places, resulting in some nearly unique errors like these:
invalid command \012cal_item',NULL);
and
invalid command \004
ERROR: syntax error at or near "cal_item_write" at character 1157529
One can visually miss them quite easily while watching for errors scrolling off the screen.
IIRC, there were also cases where users had registered with nonstandard characters in name fields. Being late for me, and my thinking a bit far fetched right now, I see how something like that might cause some incomplete import of object_id data (and relationships) and subsequently adversley affect some abstracted views and queries.
Anyway, hope this helps,
