LCShen

# With thanks to https://github.com/optoro/activerecord-callback_notification for original inspiration
if Rails.env.development?
  module ActiveRecord
    module CallbackNotifications
      extend ActiveSupport::Concern

      module ClassMethods

        def notify_all_callbacks
          # Make sure all models are loaded before trying to enumerate

LCShen

require 'rubygems'
require 'win32ole'
require 'csv'

mdb_file="c:/Sites/labs/50q.bok"

class AccessDb
    attr_accessor :mdb, :connection, :data, :fields, :catalog

    def initialize(mdb=nil)

LCShen

require 'active_record/connection_adapters/abstract_adapter'

require 'bigdecimal'
require 'bigdecimal/util'

# msaccess_adapter.rb -- ActiveRecord adapter for Microsoft Access Db
#
# "Adapted" from the sqlserver_adapter.rb for Microsoft SQL Sever:
#   Author: Joey Gibson <joey@joeygibson.com>
#

LCShen

Legacy Databases

Not every application starts from scratch, sometime you have to deal with a legacy database. Walking the Rails golden path makes life easy, and there's a perception that stepping off that path is incredibly painful.

It's not true. If your database is well designed and but doesn't follow the Rails naming conventions, it's easy to make them play nicely together. However, if your database structure is crap to begin with, then there's only so much Rails can do for you. ActiveRecord is a mapper between the database and objects, but it's not a DBA-in-a-Box.

Theory

In a green-field app, ActiveRecord and the Database fit right together:

LCShen

/**
 * A Sample CSS upgrade for Eventbrite's default event pages
 */
 
/*-----------------------------------------------------------------
Theme: No Compromises
By: The Eventbrite Design Team

To use this theme follow these five easy steps.
1) Login to your Eventbrite account. If you don't have one visit

LCShen

#!/usr/bin/ruby
require 'rss'

# Usage
# $ ./railscasts.rb http://railscasts.com/subscriptions/YOURRAILSCASTRSS/\/
#     episodes.rss
# OR
# $ ./railscasts.rb

p 'Downloading rss index'