On 16-08-2006 17:30:30 -0400, Luis Zarrabeitia wrote:
I imagined that \. could cause some semantic trouble. I went ahead anyway because I wanted "myprocess |" (or a "cat myfile |") to be able to execute more than one copyfrom and \. seemed a good choice (postgres). I shouldn't have touched the MapiClient, though. I like that you fixed it. Would be acceptable to introduce the \. without touching the MapiClient? (changes could be confined to ascii_io.mx)
In fact, the PostgreSQL dump format contains other things like \NULL or \0 (not sure which one) together with the \. to "terminate" the dump. Supporting this (in the back-end) probably means writing/patching another ascii_io called postgres_io or something :) I haven't looked into it too deep, but maybe this is for now with the current state one bridge too far.