Hi, > "NO, go away!"
Well, before adding a feature request, I usually would like to understand the real-world use case. In this case, I don't understand it so far. I know about the following two use cases for dropping columns: - Manually at development time: in this case, the developer tries to drop a column manually. If this doesn't work, a nice exception message is enough in this case. - Programmatically when installing a new version of an application: in this case, the program drops the column (for example at startup), but only if the schema is old. The program is expected to run automatically and without problems (if there is a problem, then the application is buggy, or there is something wrong with the database, both needs manual intervention). For both cases, I don't see how additional metadata would help. It seems you have a different use case... Could you please explain it? Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
