Sean Griffin 8eb536e7b4 Result sets never override a model's column type ... MySQL and PostgreSQL provide a column type override in order to properly type cast computed columns included in a result set. This should never override the known types of full fledged columns. In addition to messing up computed properties, this would have led to inconsistent behavior between a record created with `new`, and a record created with `last` on the mysql adapter in the following cases: - `tinyint(1)` with `emulate_booleans` set to `false` - `text`, `string`, `binary`, and `decimal` columns		2014-05-29 07:13:53 -07:00
..
active_schema_test.rb	Add ConnectionHelper to refactor tests.	2014-04-03 01:06:43 -07:00
case_sensitivity_test.rb	Only use BINARY for mysql case sensitive uniqueness check when column has a case insensitive collation.	2013-11-26 04:59:18 +09:00
connection_test.rb	Stringify variables names for mysql connections	2014-04-30 22:56:27 +03:00
consistency_test.rb	Result sets never override a model's column type	2014-05-29 07:13:53 -07:00
enum_test.rb
mysql_adapter_test.rb	Clean up tables after each test.	2014-03-22 17:06:41 -07:00
quoting_test.rb	Delegate Column#type to the injected type object	2014-05-19 08:07:21 -07:00
reserved_word_test.rb	Use teardown helper method.	2014-03-14 20:48:59 -07:00
schema_test.rb	Changed extract_limit in class Column to return correct mysql float and double limits	2014-05-16 01:39:24 +09:30
sp_test.rb
sql_types_test.rb
statement_pool_test.rb	Don't skip tests if we don't need to.	2013-11-08 13:59:07 -02:00