Skip to content
Commits on Jan 12, 2012
  1. @spastorino
Commits on Dec 29, 2011
  1. @joliss @vijaydev

    Document that index names are made up of all columns, not just the fi…

    joliss committed with vijaydev Dec 27, 2011
    index_name has been using the following expression
        "index_#{table_name}_on_#{Array.wrap(options[:column]) * '_and_'}"
    since at least 2006 (bc7f231), and that's how they come out in my DB.
    Please check that this is correct before merging into master, perhaps
    I'm misunderstanding the section I changed.
Commits on Dec 16, 2011
  1. @jonleighton
  2. @jonleighton
  3. @jonleighton
  4. @jonleighton

    Cache columns at the model level.

    jonleighton committed Dec 16, 2011
    Allows two models to use the same table but have different primary keys.
Commits on Dec 13, 2011
  1. @jonleighton

    Revert naive O(1) table_exists? implementation.

    jonleighton committed Dec 13, 2011
    It was a bad idea to rescue exceptions here. This can interfere with
    transaction rollbacks which seems to be the cause of current CI
    Instead, each adapter should implement its own DB-specific O(1)
    implementation, and we fall back on the generic, slower, implementation
Commits on Dec 9, 2011
  1. @tenderlove
  2. @tenderlove

    don't need a begin / end.

    tenderlove committed Dec 9, 2011
  3. @tenderlove
Commits on Dec 8, 2011
  1. @tenderlove
  2. @vijaydev

    fix nodocs

    vijaydev committed Dec 9, 2011
  3. @vijaydev

    fix comments

    vijaydev committed Dec 9, 2011
  4. @tenderlove
  5. @tenderlove
  6. @tenderlove
Commits on Dec 7, 2011
  1. @tenderlove
  2. @tenderlove
Commits on Dec 5, 2011
  1. @tenderlove
  2. @jadeforrest

    Speed up table_exists? for databases with a large number of tables

    jadeforrest committed Dec 5, 2011
    At New Relic, we have hundreds of thousands of tables, and our migrations took 30 minutes without this similar patch. This cuts it down to a more reasonable amount of time.
    The rescue false part is ugly, but necessary as far as I can tell. I don't know of a cross-database statement you can make that will work without trapping errors.
Commits on Dec 4, 2011
  1. @arunagw

    SQlite3 Bump

    arunagw committed Dec 4, 2011
Commits on Dec 2, 2011
  1. @kennyj

    Use show create table.

    kennyj committed Nov 22, 2011
  2. @fxn
Commits on Nov 29, 2011
  1. @tenderlove

    push synchronization in to each method. Reduces method calls and makes

    tenderlove committed Nov 29, 2011
    it clear which methods are synchronized.
  2. @tenderlove

    Automatic closure of connections in threads is deprecated. For example

    tenderlove committed Nov 29, 2011
    the following code is deprecated: { Post.find(1) }.join
    It should be changed to close the database connection at the end of
    the thread: {
    Only people who spawn threads in their application code need to worry
    about this change.
  3. @tenderlove
  4. @tenderlove
  5. @tenderlove
  6. @tenderlove
  7. @tenderlove
  8. @tenderlove
  9. @tenderlove
  10. @jonleighton
  11. @tenderlove
Commits on Nov 28, 2011
  1. @tenderlove
Something went wrong with that request. Please try again.