This project is archived and is in readonly mode.
[Patch] Fix AR detection of postgres interval types with precision
Reported by alan | May 15th, 2009 @ 03:34 AM | in 3.x
AR fails to detect interval types with precision, which look like 'interval(0)'. These types become improperly handled as integers. I modified the type regex to catch the possible trailing '(n)' syntax returned by postgres. Rather than include a separate test, I simply modified the postgres schema to use interval with precision, and all tests pass.
Comments and changes to this ticket
-
alan May 15th, 2009 @ 08:24 PM
This will help allow out-of-the-box functionality with databases edited or created by certain database manager suites which create intervals with precision, by default (e.g. EMS postgres manager).
-
-
Rohit Arondekar October 9th, 2010 @ 04:16 AM
- State changed from “new” to “stale”
- Importance changed from “” to “”
Marking ticket as stale. If this is still an issue please leave a comment with suggested changes, creating a patch with tests, rebasing an existing patch or just confirming the issue on a latest release or master/branches.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Jeremy Kemper
Julian Mehnle
Rohit Arondekar