From: | Jeremy Drake <pgsql(at)jdrake(dot)com> |
---|---|
To: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | large object regression tests, take two |
Date: | 2006-09-27 08:57:28 |
Message-ID: | Pine.BSO.4.64.0609270150170.16532@resin.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
This is the latest version of the large object regression test I have been
working on. Note that a prerequisite for this version of the test is the
patch I made to psql to make it not output on \lo_* commands in quiet mode
is required (also attached, it's small).
Sorry that it still makes use of the sed trickery like the copy test does,
but:
1) I think the server side lo_(import|export) functions need to be tested
as well as the psql variants
2) ISTM that making assumptions about the working directory of psql
during
the regression tests would open a can of worms, especially wrt VPATH
builds where the data files could be in a completely separate tree from
the regression tests.
Thoughts?
--
Why did the Roman Empire collapse?
What is the Latin for office automation?
Attachment | Content-Type | Size |
---|---|---|
psql-largeobj-output.patch | text/plain | 2.5 KB |
largeobj-regress-v2.patch.gz | application/octet-stream | 2.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Natoli | 2006-09-27 09:07:04 | Re: Bad bug in fopen() wrapper code |
Previous Message | Magnus Hagander | 2006-09-27 07:47:21 | Re: Bad bug in fopen() wrapper code |