[Schevo-devel] another evolution stress test

[Matthew Scott]

I haven't been able to re-create this, so I think it's something where
an XML export/import would do the trick to clean it up.  I guess
exporting is something for the 'evo' todo list, since importing is
already possible. :)

I did find a bug related to sys.links and sys.count with regards to
removing an entity field though, so that failing test is in and I will
try to make it pass soon.


On 11/13/05, Joseph Schlesinger <joes at alt2254.org> wrote:
> This one involves an extent from which a removed an f.entity() field.
> Even after editing the schema to put the field back in, I get the
> traceback (following the example code that prompts it):
>
> tx=some_entity.t.update()
> tx.name = 'foo'
> app.db.execute(tx)
> Traceback (most recent call last):
>   File "<input>", line 1, in ?
>   File "c:\code\schevo\src\schevo\database.py", line 144, in execute
>     retval = tx._execute(self)
>   File "c:\code\schevo\src\schevo\transaction.py", line 405, in _execute
>     db._update_entity(extent_name, oid, fields)
>   File "c:\code\schevo\src\schevo\database.py", line 793, in _update_entity
>     other_value = fields_by_id[referrer_field_id]
>   File "c:\code\schevo\src\schevo\store\persistent_dict.py", line 31, in
> __getitem__
>     return self.data[key]
> KeyError: 816866163
> _______________________________________________
> Schevo-devel mailing list
> Schevo-devel at lists.orbtech.com
> http://lists.orbtech.com/mailman/listinfo/schevo-devel
>


--
Matthew R. Scott