Timeline for Replacing a table with new version
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 5, 2012 at 3:18 | vote | accept | dann.dev | ||
| Jun 5, 2012 at 3:18 | comment | added | dann.dev | Interesting, and very clever, but I think it's probably overkill for what I want, I might stick with renaming the table or just creating a new one with a different name, thanks for the help. | |
| Jun 5, 2012 at 3:12 | comment | added | Aaron Bertrand | @dann.dev I have spoken about this technique before... have a look at this question for example... | |
| Jun 5, 2012 at 3:10 | comment | added | dann.dev | For every build we do we drop all permissions and apply them again, so if the name is the same it should apply all the needed permissions. I'm not sure what you mean be swapping schemas? The table isn't related to any others but there are still quite a few othe's in the schema. | |
| Jun 5, 2012 at 3:06 | history | answered | Aaron Bertrand | CC BY-SA 3.0 |