Open GoogleCodeExporter opened 9 years ago
I imagine this is related to http://www.sqlite.org/faq.html#q6
So I guess the history command should make its own connection to the database,
rather
than trying to use the connection in the History (singleton) class.
The history builtin uses search_commands() in hotwire/state.py (via
get_history() in
hotwire/shell.py).
Maybe the calls to the commands need to indicate whether they are part of the
long
running thread, or just part of a command. Or if there is only one long running
process then that thread ID could be stored in the History singleton when it is
created, and any call with a different thread ID would have it's own connection
created.
Would that be a reasonable way to do this?
Original comment by dmi...@gmail.com
on 23 May 2008 at 5:53
Original issue reported on code.google.com by
dmi...@gmail.com
on 22 May 2008 at 1:23