activerecord-postgis-array 0.3.4

data/lib/activerecord-postgis-array/version.rb

@@ -0,0 +1,3 @@
+module ActiveRecordPostgisArray
+  VERSION = '0.3.4'
+end

data/spec/arel/arel_spec.rb

@@ -0,0 +1,30 @@
+require 'spec_helper'
+
+describe 'Don\'t stomp all over the default ActiveRecord queries' do
+  let!(:adapter) { ActiveRecord::Base.connection }
+
+  before do
+    adapter.create_table :cars, :force => true do |t|
+      t.string :make
+      t.string :model
+      t.timestamps
+    end
+
+    class Car < ActiveRecord::Base
+      attr_accessible :make, :model
+    end
+  end
+
+  after do
+    adapter.drop_table :cars
+    Object.send(:remove_const, :Car)
+  end
+
+  describe 'Where Queries' do
+    describe 'Set query' do
+      it '' do
+        Car.where('id in (?)', [1,2]).to_sql.should eq "SELECT \"cars\".* FROM \"cars\"  WHERE (id in (1,2))"
+      end
+    end
+  end
+end

data/spec/arel/array_spec.rb

@@ -0,0 +1,77 @@
+require 'spec_helper'
+
+describe 'Array Column Predicates' do
+  describe 'Array Overlap' do
+    it 'converts Arel overlap statment' do
+      arel_table = Person.arel_table
+
+      arel_table.where(arel_table[:tags].overlap(['tag','tag 2'])).to_sql.should match /&& '\{"tag","tag 2"\}'/
+    end
+
+    it 'converts Arel overlap statment' do
+      arel_table = Person.arel_table
+
+      arel_table.where(arel_table[:tag_ids].overlap([1,2])).to_sql.should match /&& '\{1,2\}'/
+    end
+
+    it 'works with count (and other predicates)' do
+      arel_table = Person.arel_table
+
+      Person.where(arel_table[:tag_ids].overlap([1,2])).count.should eq 0
+    end
+
+    it 'returns matched records' do
+      one = Person.create!(:tags => ['one'])
+      two = Person.create!(:tags => ['two'])
+      arel_table = Person.arel_table
+
+      query = arel_table.where(arel_table[:tags].overlap(['one'])).project(Arel.sql('*'))
+      Person.find_by_sql(query.to_sql).should include(one)
+
+      query = arel_table.where(arel_table[:tags].overlap(['two'])).project(Arel.sql('*'))
+      Person.find_by_sql(query.to_sql).should include(two)
+
+      query = arel_table.where(arel_table[:tags].overlap(['two','one'])).project(Arel.sql('*'))
+      Person.find_by_sql(query.to_sql).should include(two)
+      Person.find_by_sql(query.to_sql).should include(one)
+    end
+  end
+
+  describe 'Array Contains' do
+    it 'converts Arel contains statement and escapes strings' do
+      arel_table = Person.arel_table
+
+      arel_table.where(arel_table[:tags].contains(['tag','tag 2'])).to_sql.should match /@> '\{"tag","tag 2"\}'/
+    end
+
+    it 'converts Arel contains statement with numbers' do
+      arel_table = Person.arel_table
+
+      arel_table.where(arel_table[:tag_ids].contains([1,2])).to_sql.should match /@> '\{1,2\}'/
+    end
+
+    it 'works with count (and other predicates)' do
+      arel_table = Person.arel_table
+
+      Person.where(arel_table[:tag_ids].contains([1,2])).count.should eq 0
+    end
+
+    it 'returns matched records' do
+      one = Person.create!(:tags => ['one', 'two', 'three'])
+      two = Person.create!(:tags => ['one', 'three'])
+      arel_table = Person.arel_table
+
+      query = arel_table.where(arel_table[:tags].contains(['one', 'two'])).project(Arel.sql('*'))
+      Person.find_by_sql(query.to_sql).should include one
+      Person.find_by_sql(query.to_sql).should_not include two
+
+      query = arel_table.where(arel_table[:tags].contains(['one', 'three'])).project(Arel.sql('*'))
+      Person.find_by_sql(query.to_sql).should include one
+      Person.find_by_sql(query.to_sql).should include two
+
+      query = arel_table.where(arel_table[:tags].contains(['two'])).project(Arel.sql('*'))
+      Person.find_by_sql(query.to_sql).should include one
+      Person.find_by_sql(query.to_sql).should_not include two
+    end
+  end
+end

data/spec/columns/array_spec.rb

@@ -0,0 +1,120 @@
+# encoding: utf-8
+
+require 'spec_helper'
+
+describe 'Array column' do
+  let!(:integer_array_column) { ActiveRecord::ConnectionAdapters::PostGISAdapter::SpatialColumn.new 'field', nil, 'integer[]'}
+  let!(:string_array_column) { ActiveRecord::ConnectionAdapters::PostGISAdapter::SpatialColumn.new 'field', nil, 'character varying(255)[]'}
+  let!(:text_array_column) { ActiveRecord::ConnectionAdapters::PostGISAdapter::SpatialColumn.new 'field', nil, 'text[]'}
+  let!(:adapter) { ActiveRecord::Base.connection }
+
+  context 'string array' do
+    describe '#type_class' do
+      context 'has null value' do
+        it 'converts the PostgreSQL value to an array with a nil value' do
+          string_array_column.type_cast('{1,NULL,"NULL"}').should eq ['1',nil,'NULL']
+        end
+      end
+
+      context 'utf8' do
+        it "handles incoming UTF8 as UTF8" do
+          string_array_column.type_cast('{"Аркалио"}').should eq ['Аркалио']
+        end
+      end
+
+      context 'corner cases, strings with commas and quotations' do
+        it 'converts the PostgreSQL value containing escaped " to an array' do
+          string_array_column.type_cast('{"has \" quote",another value}').should eq ['has " quote', 'another value']
+        end
+
+        it 'converts the PostgreSQL value containing commas to an array' do
+          string_array_column.type_cast('{"has , comma",another value,"more, commas"}').should eq ['has , comma', 'another value', 'more, commas']
+        end
+
+        it 'converts strings containing , to the proper value' do
+          adapter.type_cast(['c,'], string_array_column).should eq '{"c,"}'
+        end
+
+        it "handles strings with double quotes" do
+          adapter.type_cast(['a"b'], string_array_column).should eq '{"a\\"b"}'
+        end
+
+        it 'converts arrays of strings containing nil to the proper value' do
+          adapter.type_cast(['one', nil, 'two'], string_array_column).should eq '{"one",NULL,"two"}'
+        end
+      end
+    end
+  end
+
+  context 'text array' do
+    describe '#type_class' do
+      context 'has null value' do
+        it 'converts the PostgreSQL value to an array with a nil value' do
+          text_array_column.type_cast('{1,NULL,"NULL"}').should eq ['1',nil,'NULL']
+        end
+      end
+
+      context 'utf8' do
+        it "handles incoming UTF8 as UTF8" do
+          text_array_column.type_cast('{"Аркалио"}').should eq ['Аркалио']
+        end
+      end
+
+      context 'corner cases, strings with commas and quotations' do
+        it 'converts one element, 2 dimensional arrays' do
+          adapter.type_cast([['one','two']], text_array_column).should eq '{{"one","two"}}'
+        end
+        it 'converts the PostgreSQL value containing escaped " to an array' do
+          text_array_column.type_cast('{"has \" quote",another value}').should eq ['has " quote', 'another value']
+        end
+
+        it 'converts the PostgreSQL value containing commas to an array' do
+          text_array_column.type_cast('{"has , comma",another value,"more, commas"}').should eq ['has , comma', 'another value', 'more, commas']
+        end
+
+        it 'converts strings containing , to the proper value' do
+          adapter.type_cast(['c,'], text_array_column).should eq '{"c,"}'
+        end
+
+        it "handles strings with double quotes" do
+          adapter.type_cast(['a"b'], text_array_column).should eq '{"a\\"b"}'
+        end
+
+        it 'converts arrays of strings containing nil to the proper value' do
+          adapter.type_cast(['one', nil, 'two'], text_array_column).should eq '{"one",NULL,"two"}'
+        end
+      end
+    end
+  end
+
+  context 'integer array' do
+    describe '#type_class' do
+      context 'has null value' do
+        it 'converts a Postgres Array with nulls in it' do
+          integer_array_column.type_cast('{1,NULL,2}').should eq [1,nil,2]
+        end
+      end
+      context 'one dimensional array' do
+        it 'converts a PostgreSQL array value to an array of integers' do
+          integer_array_column.type_cast('{1,2,3,4}').should eq [1,2,3,4]
+        end
+      end
+    end
+
+    describe 'integer array to SQL statment conversion' do
+      context 'contains a nil value' do
+        it 'returns a PostgreSQL array' do
+          value = integer_array_column.type_cast('{1,NULL,2}')
+          adapter.type_cast(value, integer_array_column).should eq '{1,NULL,2}'
+        end
+      end
+      context 'one dimensional array' do
+        it 'returns a PostgreSQL array' do
+          value = integer_array_column.type_cast('{1,2,3,4}')
+          adapter.type_cast(value, integer_array_column).should eq '{1,2,3,4}'
+        end
+      end
+    end
+  end
+
+end

data/spec/dummy/.gitignore

@@ -0,0 +1,15 @@
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile ~/.gitignore_global
+
+# Ignore bundler config
+/.bundle
+
+# Ignore the default SQLite database.
+/db/*.sqlite3
+
+# Ignore all logfiles and tempfiles.
+/log/*.log
+/tmp

data/spec/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |       |-- images
+  |       |-- javascripts
+  |       `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      |-- assets
+          `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.