Administrator
|
Hi everybody,
This new version fix an important bug in UMLS support.
It also stops considering as functional properties associated with exactly-1 or max-1 restrictions. This was intended to be a feature, but was actually often more annoying that desirable.
If needed, you can restore the previous behaviour as follows:
import owlready2.prop
owlready2.prop.RESTRICTIONS_AS_FUNCTIONAL_PROPERTIES = True
Here are the changes:
* Add support for undoable destroy_entity()
* Small database optimizations
* No longer treat properties associated with exactly-1 or max-1 restriction as functional properties, returning single values instead of a list
* Bugfixes:
- Fix performance bug on UMLS mapping in PyMedTermino
Jiba
|