Mercurial > p > roundup > code
comparison test/memorydb.py @ 5317:c0cda00af479
Fix tests for memorydb and anydbm backends
The anydbm backend silently drops properties in the journal that are not
in the database during serialisation. The memorydb backend (only used
for testing) cannot deal with user changes (re-open of db under a
different user).
| author | Ralf Schlatterbeck <rsc@runtux.com> |
|---|---|
| date | Thu, 19 Apr 2018 17:03:11 +0200 |
| parents | 88fc7202f87d |
| children | 35ea9b1efc14 |
comparison
equal
deleted
inserted
replaced
| 5316:351763d6400a | 5317:c0cda00af479 |
|---|---|
| 180 | 180 |
| 181 - check the timestamp of the class file and nuke the cache if it's | 181 - check the timestamp of the class file and nuke the cache if it's |
| 182 modified. Do some sort of conflict checking on the dirty stuff. | 182 modified. Do some sort of conflict checking on the dirty stuff. |
| 183 - perhaps detect write collisions (related to above)? | 183 - perhaps detect write collisions (related to above)? |
| 184 """ | 184 """ |
| 185 | |
| 186 dbtype = "memorydb" | |
| 187 | |
| 185 def __init__(self, config, journaltag=None): | 188 def __init__(self, config, journaltag=None): |
| 186 self.config, self.journaltag = config, journaltag | 189 self.config, self.journaltag = config, journaltag |
| 187 self.classes = {} | 190 self.classes = {} |
| 188 self.items = {} | 191 self.items = {} |
| 189 self.ids = {} | 192 self.ids = {} |