Craig Miskell wrote:
>...
> Upon investigation, it turns out that when both drop and create is
> specified, that all tables currently in the map that do exist will be
> dropped, and any that do not currently exist but are in the map will be
> created, but not the ones that were just dropped.
I have not yet used Modeler to drop/create tables but I agree that you
description is not what I would have expected either.
> My gut expectation (fuelled by EOModeller in EOF), is that specifying both
> drop and create for tables will cause all necessary tables to be dropped,
> and *all* tables to be created. Typically this is quite useful during
> development, when the table structure changes periodically.
Agreed.
-h
This archive was generated by hypermail 2.0.0 : Tue Nov 26 2002 - 18:52:50 EST