Git Product home page Git Product logo

datamapper.github.com's People

Contributors

agit0 avatar akahn avatar codl avatar crantok avatar dbussink avatar dkubb avatar dlarsen avatar dmarkow avatar eik3 avatar etiennelem avatar frost avatar gyka avatar jamesgecko avatar jonjensen avatar l2g avatar lucapette avatar mkristian avatar myabc avatar namelessjon avatar nevir avatar postmodern avatar pschuegr avatar ragmaanir avatar ryanslade avatar sam avatar snusnu avatar solnic avatar somebee avatar xaviershay avatar yoshuki avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

datamapper.github.com's Issues

Bcrypt gem out of date

While installing the data_mapper gem, I got the following message:

Fetching: dm-validations-1.2.0.gem (100%)
Successfully installed dm-validations-1.2.0
Fetching: bcrypt-3.1.7.gem (100%)
Building native extensions.  This could take a while...
Successfully installed bcrypt-3.1.7
Fetching: bcrypt-ruby-3.1.5.gem (100%)

#######################################################

The bcrypt-ruby gem has changed its name to just bcrypt.  Instead of
installing `bcrypt-ruby`, you should install `bcrypt`.  Please update your
dependencies accordingly.

#######################################################

Successfully installed bcrypt-ruby-3.1.5

Maybe something to look into.

:child_key option on Associations page is incorrect

Per Relationship#child_key, the default implementation is:

property_name ||= "#{parent_name}_#{parent_property.name}".to_sym

This suggests that given a Post that belongs to an Author, the inferred child_key on the:

class Post
  belongs_to :author, :model => 'User'
end

declaration would be author_id, and not post_id as shown on the associations docs page here.

The very simple fix for this is available at http://github.com/vandrijevik/datamapper.github.com/commit/a1aa49f080f900470cd8b8546fdc6dfe30aa7660

bulk updates

Im trying to do a bulk update maybe about 30000 records , there should be a feature for a bulk update. Now it takes like 5 minutes.

New Rails 3.1 apps based on templates are missing asset handling and jQuery

A standard Rails 3.1.x app will include this in the Gemfile:

group :assets do
  gem 'sass-rails',   '~> 3.1.5'
  gem 'coffee-rails', '~> 3.1.1'
  gem 'uglifier', '>= 1.0.3'
end

gem 'jquery-rails'

group :test do
  # Pretty printed test output
  gem 'turn', '~> 0.8.3', :require => false
end

However, rails new project_name -m http://datamapper.org/templates/rails.rb doesn't preserve any of this, which makes the new app broken since any requests to /assets/* will fail.

bulk updates

Im trying to do a bulk update maybe about 30000 records , there should be a feature for a bulk update. Now it takes like 5 minutes.

site-wide search

I often find myself doing Google searches with "site:datamapper.org" - perhaps a field for such a custom search might be a useful addition to the site?

templates incompatible with Rails 3.2.1

As reported in datamapper/dm-rails#34 (comment) the templates need to remove two ActiveRecord related configuration options in config/development.rb for Rails 3.2.X:

# Raise exception on mass assignment protection for Active Record models
# config.active_record.mass_assignment_sanitizer = :strict

# Log the query plan for queries taking more than this (works
# with SQLite, MySQL, and PostgreSQL)
# config.active_record.auto_explain_threshold_in_seconds = 0.5

Another issue is that the Gemfile currently requires an older version of Rails: 3.1.3 and not 3.2.1. This change would require an update of the dependencies of dm-rails and dm-active_model to 1.2.1

Write about what DM can do that were pain points in AR

I remember switching from AR because of certain pain points, things solved by DM.

Properties in the model (so you don't have to keep checking the schema in the DB)
Better associations (through many, more than 1 step away)
Composite primary keys

Please comment with your pain points solved by DM.

Beginner Survey

We'd like to create a survey for new users of DataMapper to assess where we might improve documentation, and possibly, DataMapper itself. Comments with suggested questions are welcome.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.