I need a temp table in auth/db that looks exactly like the temp table in auth/ldap. But I don't want *that* code, thankyouverymuch.
The absolutely correct thing to do is to extend every XML class to dance tap on the top of a barrel take an "is_temporary" parameter, and to spit the right SQL when asked for it. And also the right SQL for dropping the table.
Sometimes a switch statement is just so much clearer (if ugly).
Will you kill me if I write a function in ddllib / dmllib that takes a table definition and has a big switch statement?
Or - have you got a magic trick?