pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2006-09-07	Sort PLIST.	taca	1	-20/+20

2006-02-22	Add missing file to PLIST. Bump PKGREVISION.	wiz	1	-1/+2

2004-11-27	Update ruby-vapor package to 0.81 migrating to use new framework.	taca	1	-74/+91
	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
2003-09-16	Importing databases/ruby-vapor 0.7.0 pacakge, based on PR pkg/22296	taca	1	-0/+117
	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.