David Wilson
David Wilson
Current implementation has turned into a giant mess again. Rewrite it once the data format finally stablizes
Consider including a WSGI application in the package, that can be attached to a regular web app to provide a built-in control panel for editing a database. See also issue...
This was to replace the weird 6-tuple metadata format with something more generic that could be extended in future. That work is done, and instead store metadata is a (KIND,...
Figure out what should live in acid.\* vs acid.keylib.\* vs. acid.encoders.\* vs. acid.core.\* etc., and document it Possible just get rid of acid aliases and require canonical names. Makes it...
_[Demoted to a maybe since the primary use for a Structure would be a session cookie, which would want to be encrypted, which depends on #49, which is also now...
_[Demoted to a 'maybe' since there might be too many use cases to provide a general purpose yet universally sensible encoding. Either 8-byte keys encode to a huge 40ish hex...
Eventually extract the Reddit code example into some generic function, since it's surprisingly fiddly to implement by hand. Maybe something like: ``` python @acid.meta.key def key(self): return acid.tree_key(self, 'parent_id', self.by_id)...
Given a collection with keys like: ``` 11 11 1 1 1 11 1 1 2 11 1 2 1 11 1 2 2 11 2 1 1 11 2...
This is from the old TODO list. Uniqueness can already be done using constraints in meta.py: ``` python @acid.meta.constraint def is_unique(self): return MyModel.by_some_index.get(self.must_be_unique_value) is None ``` meta.py also supports triggers,...
It might be off by one due to while loop that seeks to start key. Might also be off by one due to reverse iteration without hi= set (since first...