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 start my workflow from scratch?

What will happen to the db if I reload a tool and rerun it. Will it extend the database or will it use a new one from scratch?

You have access to the user name if you are running the tool. With that you can create a table for every user and store your data user-specific.

Cheers,
Bjoern


On Mon, Jun 16, 2014 at 11:23 PM, Björn Grüning <bjoern.gruen...@gmail.com>
wrote:

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 Galaxy database or a tool specific
database?

best,
Bjoern


  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/



___________________________________________________________
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/

Reply via email to