Sean Griffin b0f2b94dd3 Correctly handle limit on int4 and int8 types in PG ... PG doesn't register it's types using the `int(4)` format that others do. As such, if we alias `int8` to the other integer types, the range information is lost. This is fixed by simply registering it separately. The other option (which I specifically chose to avoid) is to pass the information of the original type that was being aliased as an argument. I'd rather avoid that, since an alias should truly be treated the same. If we need different behavior for a different type, we should explicitly register it with that, and not have a conditional based on aliasing. Fixes #18144 [Sean Griffin & ysbaddaden]		2014-12-22 09:55:41 -07:00
..
mysql	Fix undesirable RangeError by Type::Integer. Add Type::UnsignedInteger.	2014-12-12 00:35:48 +09:00
mysql2	Fix undesirable RangeError by Type::Integer. Add Type::UnsignedInteger.	2014-12-12 00:35:48 +09:00
postgresql	Correctly handle limit on int4 and int8 types in PG	2014-12-22 09:55:41 -07:00
sqlite3	Pass symbol as an argument instead of a block	2014-11-29 11:53:24 +01:00