From dd0f7779d89ed9436c3fb98b27cd3d449443bbc4 Mon Sep 17 00:00:00 2001
From: Alex Reisner <alex@alexreisner.com>
Date: Thu, 3 Jun 2010 09:09:25 -0400
Subject: [PATCH] Gem version bump to 0.9.2.
---
CHANGELOG.rdoc | 4 ++++
VERSION | 2 +-
rails-geocoder.gemspec | 4 ++--
3 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/CHANGELOG.rdoc b/CHANGELOG.rdoc
index 051e6546..0b10d469 100644
--- a/CHANGELOG.rdoc
+++ b/CHANGELOG.rdoc
@@ -2,6 +2,10 @@
Per-release changes to Geocoder.
+== 0.9.2 (2010 Jun 3)
+
+* Fix LIMIT clause bug in PostgreSQL (reported by kenzie).
+
== 0.9.1 (2010 May 4)
* Use scope instead of named_scope in Rails 3.
diff --git a/VERSION b/VERSION
index f374f666..2003b639 100644
--- a/VERSION
+++ b/VERSION
@@ -1 +1 @@
-0.9.1
+0.9.2
diff --git a/rails-geocoder.gemspec b/rails-geocoder.gemspec
index d8c165ce..6ba9f428 100644
--- a/rails-geocoder.gemspec
+++ b/rails-geocoder.gemspec
@@ -5,11 +5,11 @@
Gem::Specification.new do |s|
s.name = %q{rails-geocoder}
- s.version = "0.9.1"
+ s.version = "0.9.2"
s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
s.authors = ["Alex Reisner"]
- s.date = %q{2010-05-04}
+ s.date = %q{2010-06-03}
s.description = %q{Geocoder adds object geocoding and database-agnostic distance calculations to Ruby on Rails. It does not rely on proprietary database functions so finding geocoded objects in a given area is easily done using out-of-the-box MySQL or even SQLite.}
s.email = %q{alex@alexreisner.com}
s.extra_rdoc_files = [
--
GitLab