Timeline for Modifying table structure within a transaction?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 6, 2015 at 11:16 | vote | accept | Martin | ||
| Sep 29, 2011 at 16:19 | comment | added | Chris Saxon | I'd be very wary of allowing end users to modify their database structure without the assistance of a programmer/dba. Tasks such as droppping columns can't easily be undone, so writing a tool to do this and cover all possibilities will be very difficult. You could have your data model include all the possible columns and restrict each customer's view of the columns using views; these are easily re-created with different numbers of columns - something that would be much easier to do in an app. If a customer comes up with a completely new column requirement, you'd have to include it as a patch. | |
| Sep 29, 2011 at 14:03 | comment | added | Martin | Chris - "what your tool is for": Unfortunately this ASAM ODS standard isn't free to download but it's a database layout that allows for storing measurement data and associated metadata/attributes. Each customer has different attribute columns and may want to add or remove attribute columns. The tool should enable people to do this without being a programmer/dba. | |
| Sep 29, 2011 at 13:57 | comment | added | Martin | Chris - many thanks for telling me that flashback won't work anyway. That saves me a lot of thinking. | |
| Sep 29, 2011 at 11:30 | history | answered | Chris Saxon | CC BY-SA 3.0 |