Hi Melissa, Galaxy expects history datasets to be read only, so the best option (in term of this data model) might be a (read only) SQLite database (since it is just a single file on disk). They could have multiple such databases in their history or histories. If you want the user to have just one database and update it, then things are rather different... I'll let one of the Galaxy team comment. Peter On Tue, Jun 17, 2014 at 12:07 AM, Melissa Cline <cline@soe.ucsc.edu> wrote:
Hi folks,
Hopefully this is a quick question. I'm working on a set of tools that will fire off a VM from within Galaxy and will then communicate with the VM. The VM will create a local database. The vision is that this won't be a shared database; in a shared Galaxy instance, each user will have his or her own database. What is the best place to create this database under the Galaxy file system?
Thanks!
Melissa
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/