| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Instead of generating association methods directly in the model
class, they are generated in an anonymous module which
is then included in the model class. There is one such module
for each association. The only subtlety is that the
generated_attributes_methods module (from ActiveModel) must
be forced to be included before association methods are created
so that attribute methods will not shadow association methods.
|
| |
|
|\
| |
| | |
Fix ORA-00932 error when trying to insert 0 to DATE type columns.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
A recent change made to create_table does away with the
need for the block argument. Checking the arity will prevent the
mixing up of the two syntaxes.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
railties/guides/source/active_record_querying.textile
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The output in Travis is a bit different. The SQLite
documentation (http://www.sqlite.org/eqp.html) warns
output may change dramatically between releases. I
do not want to mock the result set because I want a
real EXPLAIN to happen. I prefer a test that may fail
in future releases than a test that may give false
positives in future releases.
|
|/ /
| |
| |
| |
| |
| | |
nulogy/fix_postgres_adapter_to_handle_spaces_between_schemas
Fix postgres adapter to handle spaces between schemas
|
| |
| |
| |
| |
| |
| |
| | |
"Returns true if the specified attribute has been set by the user or by
a database load and is neither nil nor empty?"
Fixes #1613
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a first implementation, EXPLAIN is highly
dependent on the database and I have made some
compromises.
On one hand, the method allows you to run the most
common EXPLAIN and that's it. If you want EXPLAIN
ANALYZE in PostgreSQL you need to do it by hand.
On the other hand, I've tried to construct a string
as close as possible to the ones built by the
respective shells. The rationale is that IMO the
user should feel at home with the output and
recognize it at first sight. Per database.
I don't know whether this implementation is going
to work well. Let's see whether people like it.
|
|\ \
| | |
| | | |
Fixed an issue id false option is ignored on mysql/mysql2 (fix #3440)
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Reasons:
* Markdown reads well as plain text, but can also be formatted.
* It will make it easier for people to read on the web as Github
formats the Markdown nicely.
* It will encourage a level of consistency when people are writing
CHANGELOG entries.
The script used to perform the conversion is at
https://gist.github.com/1339263
|
| |
| |
| |
| |
| | |
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.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
prepared statement cache
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Removed here 0d0176c4ffe5c58fd1002efbd8f7bd45a8872e33
|
| | | | |
|
|\ \ \ \ |
|
| | | | | |
|
| | | | | |
|