PyORQ 0.1 is intended to be a technology demo. I don't consider this
industrial strength software (whatever that is). In particular, PyORQ is
currently not being used in any application (although its predecessor
is). Therefore, the only testing I've done with PyORQ is the unit testing.
PyORQ 0.1 features:
- A notation for describing persistent objects, based on Python properties.
- Automatic creation of tables, based on the persistent object definition.
- A native Python notation to describe queries.
- Full support for Object Oriented programming (inheritance and
- Persistent objects may refer to other persistent objects and queries understand this.
- References to objects of a particular type may also refer to
subclasses of that type.
- Queries on a type, may return subclasses of that type.
- Interfaces to several SQL backends:
- Bugs (undoubtedly)
The biggest shortcomings of version 0.1 are:
- PyORQ does not check if the definition of a previously created persistent
object still matches the table definition
(Before modifying a persistent
db.drop_table() to remove the table).
- No support for multiple inheritance (Don't do it).
- Potential name-mangling problems are not checked
(Assume that persistent attributes are case-insensitive, and you should
- Did I mention bugs?
In upcoming versions of PyORQ I will address the shortcomings of version
0.1. In addition, I would like to:
- Support the Python types
- Support native SQL types (
- Introduce persistent lists and dictionaries.
- Add a way for persistent objects to tell the database to create an
- Let the user instantiate objects using unique keys
In later versions of PyORQ I would like to address some more complicated
- Schema evolution.
- Migration of existing databases.