Module ActiveRecord::ConnectionAdapters::DatabaseStatements
In: lib/active_record/connection_adapters/abstract/database_statements.rb

Methods

Public Instance methods

Appends LIMIT and OFFSET options to an SQL statement, or some SQL fragment that has the same semantics as LIMIT and OFFSET.

options must be a Hash which contains a +:limit+ option and an +:offset+ option.

This method modifies the sql parameter.

Examples
 add_limit_offset!('SELECT * FROM suppliers', {:limit => 10, :offset => 50})

generates

 SELECT * FROM suppliers LIMIT 10 OFFSET 50

Register a record with the current transaction so that its after_commit and after_rollback callbacks can be called.

Begins the transaction (and turns off auto-committing).

Commits the transaction (and turns on auto-committing).

Executes the delete statement and returns the number of rows affected.

Executes the SQL statement in the context of this connection.

Returns the last auto-generated ID from the affected table.

Inserts the given fixture into the table. Overridden in adapters that require something beyond a simple insert (eg. Oracle).

Checks whether there is currently no transaction active. This is done by querying the database driver, and does not use the transaction house-keeping information recorded by increment_open_transactions and friends.

Returns true if there is no transaction active, false if there is a transaction active, and nil if this information is unknown.

Not all adapters supports transaction state introspection. Currently, only the PostgreSQL adapter supports this.

Set the sequence to the max value of the table‘s column.

Rolls back the transaction (and turns on auto-committing). Must be done if the transaction block raises an exception or returns false.

Sanitizes the given LIMIT parameter in order to prevent SQL injection.

The limit may be anything that can evaluate to a string via to_s. It should look like an integer, or a comma-delimited list of integers, or an Arel SQL literal.

Returns Integer and Arel::Nodes::SqlLiteral limits as is. Returns the sanitized limit parameter, either as an integer, or as a string which contains a comma-delimited list of integers.

Returns an array of record hashes with the column names as keys and column values as values.

Returns a record hash with the column names as keys and column values as values.

Returns an array of arrays containing the field values. Order is the same as that returned by columns.

Returns a single value from a record

Returns an array of the values of the first column in a select:

  select_values("SELECT id FROM companies LIMIT 3") => [1,2,3]

Runs the given block in a database transaction, and returns the result of the block.

Nested transactions support

Most databases don‘t support true nested transactions. At the time of writing, the only database that supports true nested transactions that we‘re aware of, is MS-SQL.

In order to get around this problem, transaction will emulate the effect of nested transactions, by using savepoints: dev.mysql.com/doc/refman/5.0/en/savepoints.html Savepoints are supported by MySQL and PostgreSQL, but not SQLite3.

It is safe to call this method if a database transaction is already open, i.e. if transaction is called within another transaction block. In case of a nested call, transaction will behave as follows:

  • The block will be run without doing anything. All database statements that happen within the block are effectively appended to the already open database transaction.
  • However, if +:requires_new+ is set, the block will be wrapped in a database savepoint acting as a sub-transaction.

Caveats

MySQL doesn‘t support DDL transactions. If you perform a DDL operation, then any created savepoints will be automatically released. For example, if you‘ve created a savepoint, then you execute a CREATE TABLE statement, then the savepoint that was created will be automatically released.

This means that, on MySQL, you shouldn‘t execute DDL operations inside a transaction call that you know might create a savepoint. Otherwise, transaction will raise exceptions when it tries to release the already-automatically-released savepoints:

  Model.connection.transaction do  # BEGIN
    Model.connection.transaction(:requires_new => true) do  # CREATE SAVEPOINT active_record_1
      Model.connection.create_table(...)
      # active_record_1 now automatically released
    end  # RELEASE SAVEPOINT active_record_1  <--- BOOM! database error!
  end

Executes the update statement and returns the number of rows affected.

Protected Instance methods

Send a commit message to all records after they have been committed.

Executes the delete statement and returns the number of rows affected.

Returns the last auto-generated ID from the affected table.

Send a rollback message to all records after they have been rolled back. If rollback is false, only rollback records since the last save point.

Returns an array of record hashes with the column names as keys and column values as values.

Executes the update statement and returns the number of rows affected.

[Validate]