Browse files

- Version 1.1.4 (2009-11-07)

  - Thanks to a patch from tom taylor, Ancestry now works with different primary keys
  • Loading branch information...
1 parent 925b6a7 commit 853e453f1d3494637f0a07e39840bed34fa9bfef @stefankroes stefankroes committed Nov 7, 2009
Showing with 5 additions and 3 deletions.
  1. +3 −1 README.rdoc
  2. +2 −2 ancestry.gemspec
View
4 README.rdoc
@@ -218,8 +218,10 @@ The materialised path pattern requires Ancestry to use a 'like' condition in ord
= Version history
-The latest and recommended version of ancestry is 1.1.3. The three numbers of each version numbers are respectively the major, minor and patch versions. We started with major version 1 because it looks so much better and ancestry was already quite mature and complete when it was published. The major version is only bumped when backwards compatibility is broken. The minor version is bumped when new features are added. The patch version is bumped when bugs are fixed.
+The latest and recommended version of ancestry is 1.1.4. The three numbers of each version numbers are respectively the major, minor and patch versions. We started with major version 1 because it looks so much better and ancestry was already quite mature and complete when it was published. The major version is only bumped when backwards compatibility is broken. The minor version is bumped when new features are added. The patch version is bumped when bugs are fixed.
+- Version 1.1.4 (2009-11-07)
+ - Thanks to a patch from tom taylor, Ancestry now works with different primary keys
- Version 1.1.3 (2009-11-01)
- Fixed a pretty bad bug where several operations took far too many queries
- Version 1.1.2 (2009-10-29)
View
4 ancestry.gemspec
@@ -5,8 +5,8 @@ Gem::Specification.new do |s|
s.description = 'Organise ActiveRecord model into a tree structure'
s.summary = 'Ancestry allows the records of a ActiveRecord model to be organised in a tree structure, using a single, intuitively formatted database column. It exposes all the standard tree structure relations (ancestors, parent, root, children, siblings, descendants) and all of them can be fetched in a single sql query. Additional features are named_scopes, integrity checking, integrity restoration, arrangement of (sub)tree into hashes and different strategies for dealing with orphaned records.'
- s.version = '1.1.3'
- s.date = '2009-11-01'
+ s.version = '1.1.4'
+ s.date = '2009-11-07'
s.author = 'Stefan Kroes'
s.email = 's.a.kroes@gmail.com'

0 comments on commit 853e453

Please sign in to comment.