It will read single index from index file (ie. generated in :py:meth:`._add_single_index`).
Then it will perform ``exec`` on that code
+ If error will occur the index file will be saved with ``_broken`` suffix
:param ind: index name (will be joined with *p*)
:returns: new index object
def edit_index(self, index, reindex=False, ind_kwargs=None):
Allows to edit existing index.
+ Previous working version will be saved with ``_last`` suffix (see :py:meth:`.revert_index`
- :param bool re
dindex: should be the index reindexed after change
+ :param bool reindex: should be the index reindexed after change
Here you will find some questions and answers
+Is it production ready ?
+ We already use it in several projects. Even currently we care about backwards compatible changes. It's **ready for production use**.
What about JOINs (known from SQL databases) ?
You can write database function. Please see :ref:`join_like1`. Just remember CodernityDB is *not* relational database.
CodernityDB pure python, fast, NoSQL database
-CodernityDB is opensource, pure Python (no 3rd party dependency), fast (50 000 insert and 100 000 get operations per second, check :ref:`speed` if you don't believe in words), multi platform, schema-less, NoSQL_ database.
+CodernityDB is opensource, pure Python (no 3rd party dependency), fast (even 100 000 insert and more than 100 000 get operations per second, check :ref:`speed` if you don't believe in words), multi platform, schema-less, NoSQL_ database.
.. image:: CodernityDB.png
.. _NoSQL: http://en.wikipedia.org/wiki/NoSQL
.. _KnockoutJS: http://knockoutjs.com/
.. _Apache 2.0: http://www.apache.org/licenses/LICENSE-2.0.html