Monday, 3. April 2006 00:37.
Committed revision 361. I splitted Store into BaseStore and started a new class VolatileStore. This is not yet usable, and I am not sure whether it makes sense.The idea of is: certain tables (e.g. Currencies) will perhaps be maintained by a central maintainer who distributes his service in form of Python code (basically a Populator). The user may choose to never really store these tables in a database but to populate this data on each database startup. Most test cases currently work like this. The use the ":memory:" filename for the sqlite connection so that there is almost no performance slowdown. But still adamo generates SQL strings, and sqlite parses them, returning tuples of atomic SQL values which adamo converts back to internal atomic values and finally instances of DataRow. This is a lot of conversion, but it saves me from implementing myself the sorting and filtering code.
(to be continued)