| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / / / / |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is to avoid confusing newbies, and to be consistent with the fact
that other options like :foreign_key already allow a symbol or a string.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Sexier migrations
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Now you can omit |t| block parameter and all the t. from your migration code, that means, the syntax looks more Rails-3-ish, like the routes DSL and ActionMailer DSL.
Also, this change won't break any of your existing migration files, since the traditional syntax is still available.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Preserve SELECT columns on the COUNT for finder_sql when possible
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Building the conditions of a nested through association could
potentially modify the conditions of the through and/or source
association.
This is a Bad Thing.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If a record is removed from a has_many :through, all of the join records
relating to that record should also be removed from the through
association's target.
(Previously the records were removed in the database, but only one was
removed from the in-memory target array.)
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes #3425.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes creating records in a through association with a polymorphic source
type.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change reduces churn in the db/development_structure.sql file when using :sql as
active_record.schema_format, and makes comparing diffs much easier.
Test ensures the output SQL-statements are lexically ordered by version.
|
|\ \ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
across web workers.
|
| | | | | | | |
|
| | | | | | | |
|
|\ \ \ \ \ \ \ |
|
| | | | | | | | |
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | |/ / / / / /
| |/| | | | | |
| | | | | | | |
| | | | | | | | |
dmitriy-kiriyenko/drop_test_database_in_development_when_running_rake_db_drop
When running "rake db:drop" also drop test database in development environment
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \ |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Yes, we're on Rails 3.1 now.
|
| | | | | | | | | |
|
| |/ / / / / / / |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Postgres: Do not attempt to deallocate a statement if the connection is no longer active.
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
fixes #3335
|
| |\ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Exclude _destroy parameter in :all_blank check (issue #2937)
|
| | | | | | | | | |
|
| |/ / / / / / / |
|
| |\ \ \ \ \ \ \ |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
'Type' is a reserved column for STI. Changed conditions example to
avoid using that column name as an example. The example isn't
STI-related (and mentioning STI here is needless clutter), so changing
to avoid accidentally encouraging users to use 'type' as a column name
for other purposes.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
|/ / / / / / / / |
|
|/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | | |
stores [DHH]
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
case sensitive collation.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Use quotes for command substitution
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
maintain appropriate linkage with AR database connection across threads
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
Use the schema_search_path in prepared statements.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
To allow the use of prepared statements when changing schemas in
postgres, the schema search path is added to the sql key.
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | | |
db:test:clone_structure if path to .sql file contains spaces or dashes
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Leaving the path unquoted causes errors in paths containing spaces or dashes.
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
You can use multiple databases in your tests without disabling transactional fixtures.
|
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
An association between two models cannot be made if a relevant key is
unknown, so fail fast rather than generating invalid SQL. Fixes #3207.
|
| |/ / / / / / / /
|/| | | | | | | |
| | | | | | | | |
| | | | | | | | | |
This reverts commit ee2be435b1e5c0e94a4ee93a1a310e0471a77d07.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
If we don't have a primary key when we ask for it, it's better to fail
fast. Fixes GH #2307.
|
|/ / / / / / / /
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
running :load_config alone will lead to the dumper being run without including extensions such as those included in foreigner and spatial_adapter.
This reverses a change made here: https://github.com/rails/rails/commit/5df72a238e9fcb18daf6ab6e6dc9051c9106d7bb#L0L324
I'm assuming here that :load_config needs to be invoked separately from :environment, as it is elsewhere in the file for db operations, if not the alternative is to go back to "task :dump => :environment do".
Signed-off-by: José Valim <jose.valim@gmail.com>
|
| |/ / / / / /
|/| | | | | | |
|