#46 CASCADE for "DROP statements" (under SQL Code Generation)

[Randolf C. Richardson]

We need an SQL generation option to add "CASCADE"
parameter to all "DROP TABLE statements" because
this feature fails to drop tables when Foreign Keys are
used to reference other tables.

This should be an indented checkbox that is disabled by
default (so as not to change existing behaviour expected
by long-time Druid users -- this could be a nasty suprise
for some if it is enabled by default).

Documentation for the CASCADE parameter for
PostgreSQL can be found here (it should be the same for
other databases that support referential integrity as well):

http://www.postgresql.org/docs/8.0/interactive/sql-
droptable.html

[Andrea Carboni]

Logged In: YES
user_id=109751

DROP statements are issued in reverse order in order to avoid problems
with foreign keys. Do you still have problems? Can you show a use case?

Thanks.