Hi Melissa,
Am 17.06.2014 01:07, schrieb Melissa Cline:
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.
Are we talking here about a local
Good thing to clarify: this is a tool-specific database, created by tools
that are running inside Galaxy but that should persist after the individual
tools are done with their execution.
On Mon, Jun 16, 2014 at 11:23 PM, Björn Grüning bjoern.gruen...@gmail.com
wrote:
Hi Melissa,
Am
Hi,
Am 17.06.2014 21:25, schrieb Melissa Cline:
Good thing to clarify: this is a tool-specific database, created by tools
that are running inside Galaxy but that should persist after the individual
tools are done with their execution.
Should it persist as output data or forever even if I
Hi Björn,
The database should persist forever, even if the workflow is restarted.
I'm not sure about the distinction between forever and output data, but
the database should remain in place until the user takes specific action to
make it go away.
If you reload a tool, it will reload/extend the
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
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
