Wilson Bilkovich wrote:
If the Oracle adapter is going to assume a particular type for DATE fields (and I think it should, for sure), shouldn't it default to one that can handle the full range of dates that the Oracle DATE type can represent? I know I've seen Rails apps that store dates prior to 1970, and there will likely be many more in the future.
Isn't that (the restricted range of Ruby Time's) a general issue, not just for Oracle. Store a datetime in mysql prior to 1970 and you have the same problem, no?
As an aside, on Debian at least Time's go back to 1902, given it's support for negative time_t.
One approach would be to catch out-of-range errors and return a DateTime instead of a Time. Though from what I hear, they suck (on performance). Again though, this seems to be a general issue, not Oracle specific.
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
