Re: dropping table in testcase alter_table.sql

On Jul 12, 2011, at 4:46 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On fre, 2011-07-08 at 22:27 -0400, Robert Haas wrote:
>> On Fri, Jul 8, 2011 at 1:45 AM, Ashutosh Bapat
>> <ashutosh(dot)bapat(at)enterprisedb(dot)com> wrote:
>>> I think, tab1 and tab2 are too common names, for anyone to pick up for the
>>> tables. Also, the test alter_table.sql is dropping many other tables (even
>>> those which have undergone renaming), then why not these two?
>>
>> Beats me, but I don't see any particular value to changing it.
>
> It has occurred to me a few times that it could be useful to clarify the
> approach here. If we could somehow have a separable cleanup step for
> every test, and eliminate interdependencies between tests, we could more
> easily support a number of uses cases such as creating a completely
> populated regression test database for playing, or running tests in
> random order or in differently parallelized scenarios.

True.

...Robert