Hi Shannon, If your tiny dataset is read-mostly (that is, if it rarely if ever is updated or added to), then I would say it is OK. The only disadvantage that I know of with sharing a modules db with content is that it might cause your modules to need to be re-cached more often, when other content is loaded.
Also, it depends if you gain any advantages from doing this, which you might (such as relative paths between your code and your content, ability to back it all up in one shot, etc). So it depends. -Danny -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Shannon Sent: Thursday, June 07, 2012 2:44 PM To: General MarkLogic Developer Discussion Subject: [MarkLogic Dev General] Same database for modules and data Hello MarkLogicians, et al., I am thinking about loading my tiny dataset in my modules database--Is this an OK practice? Or is it best practice to keep them separate? Thanks, Shannon ([email protected]) _______________________________________________ General mailing list [email protected] http://community.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://community.marklogic.com/mailman/listinfo/general
