Re: [Gnumed-devel] removing test data

[Jim Busser]

On 7-Aug-09, at 8:55 AM, Karsten Hilbert wrote:

I have added the following script which will enable people

to delete most test data on a stock v11 database.

Thank you, *so* much... you are lifting, or making possible to lift, some pesky annoyances from many people :-)

We cannot

add that to the upgrade/bootstrap because it would unfixably

break the data consistency tests. People will have to run it

manually.

If I understand correctly, we hope / expect that this script will work provided that a person would run it *manually* (from the command line), but it should be ok to run it without any other special preparation steps, even immediately after running upgrade / bootstrap?

In which case is it any different if one would run a script that would

- call bootstrap, and then

- call the drop script

??

I will provide two more scripts: one that drops data for the

"Hilbert" test persons and one that drops Kirk and McCoy.

I imagine that dropping this other data requires dropping records from a wider variety of tables. Once the task of crafting the sql is complete, is there a reason the additional code cannot be appended together, into a single script? Maybe it is desirable to keep them separate only because it is planned that in v12 and above to bootstrap more demo data connected to any of Hilbert test persons and Kirk or McCoy. The separation may make it easier to maintain the respective drop scripts going forward?

Might be helpful to keep such scripts together inside a single directory. If not already too late, might such scripts be placed

inside bootstrap

inside a yet-to-be-created "delete" or "del" directory?

Might a drop_demo_patients script tie together (run) each of the component scripts?