Made a couple of useless ones, now they're just taking up space..
Is there a way to delete a module?
Débuté par
Incognito JC
, nov. 07 2009 04:55
Retour en haut
#2
Posté 07 novembre 2009 - 05:12
JasonNH
-
- Members
- 237 messages
Not in this release. 
You can prevent it from taking up some disk space by deleting it from your documents directory, but it will always appear in the Manage Modules box until they give us a new version that supports it.
You can prevent it from taking up some disk space by deleting it from your documents directory, but it will always appear in the Manage Modules box until they give us a new version that supports it.
#3
Posté 07 novembre 2009 - 05:20
Incognito JC
-
- Members
- 693 messages
Here's to hoping Bioware will include a delete function in the near future..
#4
Posté 07 novembre 2009 - 05:46
Raith Veldrin
-
- Members
- 10 messages
Here's an uninformed thought..is it because a 'module' is essentially a SQL Express database and there's not currently a built-in way to delete a DB at the moment? In other words, could a module be effectively removed using SQL Management Studio without negative reprocussions?
I hesitate to test it because perhaps 'Manage Modules' does more than look for the available DB's in the instance...plus I could be completely off in the first place
I hesitate to test it because perhaps 'Manage Modules' does more than look for the available DB's in the instance...plus I could be completely off in the first place
#5
Posté 07 novembre 2009 - 05:52
JasonNH
-
- Members
- 237 messages
Raith Veldrin wrote...
Here's an uninformed thought..is it because a 'module' is essentially a SQL Express database and there's not currently a built-in way to delete a DB at the moment? In other words, could a module be effectively removed using SQL Management Studio without negative reprocussions?
I hesitate to test it because perhaps 'Manage Modules' does more than look for the available DB's in the instance...plus I could be completely off in the first place
Yeah .. you first bud.
#6
Posté 07 novembre 2009 - 08:20
BryanDerksen
-
- BioWare Employees
-
- 273 messages
All of the modules are stored in a single database, so unfortunately it's not as easy as that. We would have included that feature already if it was (a "delete module" feature was one of my own first suggestions too when I first started working with this toolset 
). The thing that makes it difficult to implement is that the toolset strictly enforces reference integrity. When one resource references another one, for example when a creature references a conversation, it won't let you delete the referenced resource out from under the referencer. This prevents broken references from occurring, but it also makes it tricky deleting large amounts of interrelated resources. You can even get situations where there are circular references (eg a stage is in an area, and the area is referenced by the stage) that require you to edit the resource to remove references before you can delete them.
The end user toolset is basically a slightly modified version of our internal toolset, and the ability to delete modules is not something we've needed internally so we didn't have the developer resources to devote to cracking this particularly annoying little nut. It wasn't as high a priority as the other stuff we needed to fix first.
For now I'd advise simply ignoring the unneeded modules. If you really need to give your database a cleaning, you could use the builder-to-builder feature to save the modules you want to keep and then use the database restore script tucked away in the DatabaseUtilities directory to restore a fresh empty database, then re-import the stuff you saved. But this is a complex and somewhat tricky process so I would advise against it unless you had a specific reason for needing to do it or were really comfortable with the steps involved.
). The thing that makes it difficult to implement is that the toolset strictly enforces reference integrity. When one resource references another one, for example when a creature references a conversation, it won't let you delete the referenced resource out from under the referencer. This prevents broken references from occurring, but it also makes it tricky deleting large amounts of interrelated resources. You can even get situations where there are circular references (eg a stage is in an area, and the area is referenced by the stage) that require you to edit the resource to remove references before you can delete them.The end user toolset is basically a slightly modified version of our internal toolset, and the ability to delete modules is not something we've needed internally so we didn't have the developer resources to devote to cracking this particularly annoying little nut. It wasn't as high a priority as the other stuff we needed to fix first.
For now I'd advise simply ignoring the unneeded modules. If you really need to give your database a cleaning, you could use the builder-to-builder feature to save the modules you want to keep and then use the database restore script tucked away in the DatabaseUtilities directory to restore a fresh empty database, then re-import the stuff you saved. But this is a complex and somewhat tricky process so I would advise against it unless you had a specific reason for needing to do it or were really comfortable with the steps involved.
