oriolgual

# Public: A module to be mixed in another class with common methods to index
# records in ElasticSearch.
#
# The host object needs to respond to 'indexed_attributes', which will return
# an array of the attributes names to be indexed.
#
# It's also recommended to override the 'save?' method to make sure only
# records that match some specifications are indexed.
#
# The type used for the ElasticSearch index will be extracted from the name of

kapkaev

$ redis-cli
> config set stop-writes-on-bgsave-error no

kurenn

##Userable
module Userable
  def self.included(base)
    base.has_one :user, :as => :userable, :dependent => :destroy, :autosave => true
    base.validate :user_must_be_valid
    base.alias_method_chain :user, :autobuild
    base.extend ClassMethods
    base.define_user_accessors
  end
  

ndarville

Business Models

Advertising

Models	Examples
Display ads	Yahoo!
Search ads	Google

cpjolicoeur

I'm hunting for the best solution on how to handle keeping large sets of DB records "sorted" in a performant manner.

Problem Description

Most of us have work on projects at some point where we have needed to have ordered lists of objects. Whether it be a to-do list sorted by priority, or a list of documents that a user can sort in whatever order they want.

A traditional approach for this on a Rails project is to use something like the acts_as_list gem, or something similar. These systems typically add some sort of "postion" or "sort order" column to each record, which is then used when querying out the records in a traditional order by position SQL query.

This approach seems to work fine for smaller datasets, but can be hard to manage on large data sets with hundreds (or thousands) of records needing to be sorted. Changing the sort position of even a single object will require updating every single record in the database that is in the same sort group. This requires potentially thousands of wri

cjolly

newpg=9.6.1 # set to new PG version number
oldpg=`pg_config --version | cut -d' ' -f2`

# PG 96. upgrades the readline to v7, which breaks anything linked against readline v6, like ruby via ruby-build. 
# I *think* this should prevent it from installing v7. But if weird shit happens with various rubies, 
# you'll have to reinstall them.
brew pin readline

# Stop current Postgres server
brew services stop postgresql

gingerlime

#!/bin/bash

usage()
{
cat << EOF
usage: $0 options

This script set ownership for all table, sequence and views for a given database

Credit: Based on http://stackoverflow.com/a/2686185/305019 by Alex Soto

them0nk

#Model 

@user.should have(1).error_on(:username) # Checks whether there is an error in username 
@user.errors[:username].should include("can't be blank")  # check for the error message 

#Rendering
response.should render_template(:index)

#Redirecting 
response.should redirect_to(movies_path)

dhh

class PostsController < ActionController::Base
  def create
    Post.create(post_params)
  end
  
  def update
    Post.find(params[:id]).update_attributes!(post_params)
  end

  private

kinopyo

# in spec/support/omniauth_macros.rb
module OmniauthMacros
  def mock_auth_hash
    # The mock_auth configuration allows you to set per-provider (or default)
    # authentication hashes to return during integration testing.
    OmniAuth.config.mock_auth[:twitter] = {
      'provider' => 'twitter',
      'uid' => '123545',
      'user_info' => {
        'name' => 'mockuser',