Hi All, I'm happy to announce that we have released DataMapper 1.2.0.rc1.
Installation instruction (assuming you're using postgres): gem install datamapper dm-postgres-adapter --pre This pre-release should work with latest Rails 3.1.0. It also comes with many bug fixes, performance improvements and internal refactors. Please feel free to test it and report any issues on Github: https://github.com/dm-core/issues Here's a list of the most important changes: dm-core: - STI queries no longer include the top-level class name - UnderscoredAndPluralizedWithoutLeadingModule naming convention was added - belongs_to supports :unique option - Validation of property names was improved - Resource[] and Resource[]= no longer fail when property name is not known - Redundant usage of chainable was removed resulting in a better performance - Boolean property typecasting was refactored - Various issues with setting default Property options were fixed - Resource#attributes= no longer use public_method_defined? - this is a security fix preventing possible DDOS attacks - Problems with auto-migrations in multiple repositories were fixed dm-adjust: - Support for InMemoryAdapter - Add COALESCE to default NULL columns to 0 dm-constraints: - Total rewrite dm-do-adapter: - Warning from DO is gone now dm-migrations: - alter table is fixed for postgres - Property options (such as :length) are now correctly used in migrations - Support to specify table options when creating a table was added (for things like db engines in mysql etc.) dm-rails: - Support for Rails 3.1.0 - Storage create/drop tasks are by default noops in case an adapter doesn't support it - Support for field_naming_convention option - Support for resource_naming_convention option - You can now set a custom repository scope for the repository in the IdentityMap middleware dm-serializer: - *Should* work with psych dm-types: - Support for Resource#dirty? upon indirect property mutation was added (this is huge, more info here: https://github.com/datamapper/dm-types/commit/3d96b1cd2b270a3843877a5eb542da808df7b986) - Issues with Paranoid properties and STI were fixed - JSON property uses multi_json now dm-validations: - #valid? is always called even if a resource is not dirty - Issues with JRuby and unicode were fixed - Massive internal clean-up towards future rewrite that will make validations even more awesome For a full list of all the commits you can check out this gist: https://gist.github.com/1206542 It's probably worth to mention that the focus of development is slowly changing towards DataMapper 2.0. We want to get 1.2.0 final released as soon as possible and then continue working on the libraries that will be a part of DataMapper 2.0. There's also a big rewrite of dm- validations that will be included in the 1.3.0. We will of course continue to support and maintain 1.x.x series. It's hard to say how many 1.x releases will go out until 2.0 is ready though. If you are interested in the development of DataMapper 2.0 you can read the roadmap that we're preparing: https://github.com/datamapper/dm-core/wiki/roadmap And as always feel free to ask any questions in #datamapper IRC channel. Thank you to all of the contributors! Cheers! # solnic -- You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/datamapper?hl=en.
