Skip to content
This repository was archived by the owner on Nov 9, 2017. It is now read-only.

Fixes Issue #33 #35

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

descentintomael
Copy link

This updates spatial_adapter to be able to work with ActiveRecord 3.2.0 and above.

panthomakos and others added 6 commits September 27, 2011 10:16
- Upgraded the gem structure to use a more generic rubygems gemspec.
- Added a Gemfile to install development dependencies for easier
  testing.
- Added bundler require to simplify code in specs and lib.
- Updated the README.rdoc file to include testing information.
- Added support for the jdbcmysql adapter.
- Consolidated common mysql code and tests to conform to DRY principles.
  There was a lot of replicated code in tests and mysql related files
  that is now shared in modules.
- Upgraded tests to be compliant with the new rspec format.
- Upgraded tests to be compliant with the new SchemaDumper format.
- Removed jeweler related gemspec that was hacked into the Rakefile.
- Added a .gitignore file.
Conflicts:
	README.rdoc
	lib/spatial_adapter/version.rb
	spec/db/jdbcmysql_raw.rb
Conflicts:
	lib/spatial_adapter/version.rb
@jywarren
Copy link

Hmm, doesn't seem to work on mysql (as opposed to mysql2). I get:

uninitialized constant ActiveRecord::ConnectionAdapters::MysqlColumn

on line 52 of /vendor/plugins/spatial_adapter/lib/spatial_adapter/mysql.rb

I'm going to try fixing this and will report back if I find anything that works.

@alexspeller
Copy link

Any chance of getting this merged and pushed to rubygems? Currently the gem is broken with new rails apps and having to hunt down a fork to get it to work is not ideal. Thanks!

@alexspeller
Copy link

Oh, I only just noticed the "no longer in active development" bit. Nevermind!

@pdeffendol
Copy link
Owner

Yup, I'm not planning to merge anything else in here. I'd recommend using RGeo has it has a better architecture, more features, and 3.2 compatibility. If someone would like to take over I'd be happy to get things switched around on rubygems.org so you can continue making releases.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants