developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
Version 0.81 (tagged 22 Nov 2003, revision 279)
Bug Fixes:
* correct mistake in Usage Example, operator for wildcard searching
is ~, not =
* raise proper errors on various methods of Persistable when no
PersistenceManager is available, instead of NoMethodError
Version 0.80 (tagged 19 Nov 2003, revision 275)
Features:
* transaction logging, record information about time, committer and log
message as well as list of objects modified per transaction
* basic versioning support, retrieval of historic object states
* vaporadmin: removal of classes and all their instances using the "remove" command
* vaporadmin: modification of class' metadata using the "update" command
* new operator (~) for wildcard searches on Strings
Bug Fixes:
* allow SQL keywords as names of persistent attributes
* fix bug where camelCase variables would not be correctly set on object loading
* correctly transfer newly persistent objects back to transient state during
rollback(). This bug caused incomprehensible ObjectDeletedErrors when manually
or automatically rolling back.
* check REXML::Version instead of REXML::VERSION_MAJOR, which does not exist
in the REXML version that is included in Ruby 1.8
* minimize number of warnings issued when using `ruby -w', including those
from Ruby 1.8.x, that are issued regardless of -w
Incompatible Repository Changes: (Repository needs to be recreated from scratch)
* repository schema version 3
* add fields and tables for versioning
by Rasputin <rasputin at idoru dot mine dot nu>.
Vapor is a persistent Object-Repository for Ruby, providing
transparent persistence of Ruby objects to a PostgreSQL database.
It's goal is to provide developers with an easy-to-use persistence
framework that does not interfere with the code of classes that
are to be persistently stored.
Vapor does not require any knowledge about relational databases,
so developers can concentrate on the task of writing their application logic.
Some of Vapor's general design was inspired by the JDO
(Java Data Objects) standard.
