** Branch linked: lp:~jplacerda/zeitgeist/660307
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/660307
Title:
zeitgeist fails to run if its database structure is not
Public bug reported:
In order to make handling cursors / connections in sql.py, we should
create a function _connect_to_db which does exactly that.
19:34 thekorn I think we should make these lines a new method, like
connect_to_database:
19:34 thekorn Iconn = sqlite3.connect(file_path)
19:34
Public bug reported:
There are quite a few clean-ups that are possibly in sql.py.
I've already made a few of these cleanups, but some more complex one's would
have to rely on better sql tests:
10:16 jplacerda thekorn: back to sql.py... :) In create_db if the database
is not new, and it is up
Things have changed slightly:
I implemented Mikkel's suggestion of setting the version to -1 just
before an upgrade, and back to it's correct value afterwards. This is
only useful if an upgrade is killed: the upgrade can also fail due to a
raised OperationalError. If that is the case (regardless
Public bug reported:
21:43 RainCT jplacerda: So there's a problem with the test system. It's
supposed to set ZEITGEIST_DATA_PATH to a temporary directory, but it's only
doing so for doctests (of which we don't have any anymore)
21:44 jplacerda I was just looking at engine-test and something
This still needs more work :)
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/784011
Title:
clean up sql.py
Status in Zeitgeist Framework:
New
Bug description:
There
12:46 thekorn jplacerda: wow, great. the main question is: do we wan to be
the cool kids on the block, or is it enough for us to do it the old school way?
12:47 thekorn if we want to be on the cool side of life, and use the state
of the art python way to handle such situations, we propable
First off, thanks to Jacob for taking the time to provide such complete
use cases / examples / API suggestions, these are much appreciated! I
agree that this is an issue which needs to be tackled. The crux of the
matter, as outlined by Jacob, is that Zeitgeist is enabled by default in
11.04, while
Here's an update on our recent efforts:
1) RainCT and I have been packaging sqlcipher -- I don't think it should take
us much longer to finish (RainCT can probably give a better estimate);
2) I have confirmed (via LD_PRELOAD) that sqlcipher somewhat works with the
existing pysqlite bindings, we
I now have the python bindings working -- all that remains is
packaging.
** Branch linked: lp:~jplacerda/+junk/python-sqlcipher
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
** Branch linked: lp:~jplacerda/zeitgeist/encryption
--
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.
https://bugs.launchpad.net/bugs/787868
Title:
Encryption of database
Status in Zeitgeist Framework:
After talking with the maintainer of sqlcipher, I'm now using the v2beta
branch, which provides an sqlcipher_export function, making my life much
easier. I'm exposing this function to python-sqlcipher (the bindings),
and then making use of it within Zeitgeist. Basically, this allows us to
attach
12 matches
Mail list logo
