Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Move `resolve_sti_reflections` which is table row related code into `TableRow` | Ryuta Kamizono | 2018-11-03 | 1 | -88/+3 |
| | |||||
* | Don't pass useless `table_name` to `ModelMetadata.new` | Ryuta Kamizono | 2018-11-03 | 1 | -1/+1 |
| | | | | | | | The `model_metadata` is only used if `model_class` is given. If `model_class` is given, the `table_name` is always `model_class.table_name`. | ||||
* | Avoid violating key constraints in fixture HABTM associations | James Le Cuirot | 2018-10-29 | 1 | -0/+3 |
| | | | | | | | | | When loading fixtures, Ruby 1.9's hash key ordering means that HABTM join table rows are always loaded before the parent table rows, violating foreign key constraints that may be in place. This very simple change ensures that the parent table's key appears first in the hash. Violations may still occur if fixtures are loaded in the wrong order but those instances can be avoided unlike this one. | ||||
* | Move FixtureSet::ReflectionProxy and FixtureSet::HasManyThroughProxy to ↵ | Gannon McGibbon | 2018-10-05 | 1 | -0/+32 |
| | | | | FixtureSet::TableRows | ||||
* | Introduce FixtureSet::TableRows and FixtureSet::TableRow | Gannon McGibbon | 2018-10-05 | 1 | -0/+97 |