| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / / / |
|
|/ / /
| | |
| | |
| | | |
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>
|
| |/ /
|/| | |
|
|\ \ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Closes #2807.
|
| | | |
| | | |
| | | |
| | | | |
Fix: habtm doesn't respect select query method
|
| | | |
| | | |
| | | |
| | | | |
Closes #3104.
|
|/ / /
| | |
| | |
| | | |
mutating the array. Fixes #3020.
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
|/ / / |
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
There is no meaningful performance penalty in defining attribute
methods, since it only happens once.
There is also no reason *not* to define them, since they get thrown in
an included module, so they will not 'overwrite' anything. In fact, this
is desirable, since it allows us to call super.
|
| | | |
| | | |
| | | |
| | | | |
We can just use method_defined? and private_method_defined?
|
|/ / /
| | |
| | |
| | |
| | | |
For consistency with find_or_initialize_by. Also remove first_or_build
alias.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This shouldn't ever happen unless people are doing something
particularly weird, but adding a deprecation in case there are bugs not
caught by our tests.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Check respond_to_without_attributes? in method_missing. If there is any
method that responds (even private), let super handle it and raise
NoMethodError if necessary.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes a situation I encountered where a subclass would cache the
name of a generated attribute method in @_defined_class_methods. Then,
when the superclass has it's attribute methods undefined, the subclass
would always have to dispatch through method_missing, because the
presence of the attribute in @_defined_class_methods would mean that it
is never generated again, even if undefine_attribute_methods is called
on the subclass.
There various other confusing edge cases like this. STI classes share
columns, so let's just keep all the attribute method generation state
isolated to the base class.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously we would just silently write the attribute. This can lead to
subtle bugs (for example, see the change in AutosaveAssociation where a
through association would wrongly gain an attribute.
Also, ensuring that we never gain any new attributes after
initialization will allow me to reduce our dependence on method_missing.
|
| | |
| | |
| | |
| | | |
Make sure we don't redefine an already-defined attribute method.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
db:migrate:status not looking at all migration paths
|
|\ \ \
| | | |
| | | | |
Add first_or_create family of methods to Active Record
|
| | | |
| | | |
| | | |
| | | | |
of methods.
|
| | | |
| | | |
| | | |
| | | | |
removing examples that create several users at the same time (this is confusing and not really helpful).
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Active Record.
This let's you write things like:
User.where(:first_name => "Scarlett").first_or_create!(:last_name => "Johansson", :hot => true)
Related to #2420.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* https://github.com/rails/rails:
Postgresql adapter: added current_schema check for table_exists?
Postgresql adapter: added current_schema check for table_exists?
|