apeiros why do you need reasons? Using with ruby/rails can be inconvenient, way more time is spent on MySQL and postgresql support in our community. Calling stored procedures with output parameters can be challenging, but I think that was the biggest problem. That and threading issues with the driver we were using and unicorn.
There was a project a few years ago trying to get at least 1-100 done, I think it was a fight against the maintainers that said NO
apeiros That's how it was with my client. Somehow someone convinced them they needed an API, and it should be written in ruby. They did great sales job but sucked at implementation and I was brought in to clean up the mess. They're a .NET shop, had ASP.NET and MVC experience and were MS SQL. Everything was in stored procedures. I told the client many times to just scrap the ruby project and do it in .NET
Anyone alive in here? I need to tell ActiveRecord to piss off when it comes to timezones (don't convert time to anything, local or UTC, just take what I give it and put it in the database). Like Sequel's timezone = nil option. Is there an easy way to do that (or to override the introspected type to make it a string?)
time_zone_aware_attributes, skip_time_zone_conversion, write_, _before_type_conversion, none of them do what I hope.
Is there a way to override the introspected type on AR Models? Crazy legacy system and it would make my life easier to treat DateTime columns as strings. Several apps touch the same db, and they all assume DateTime stored as tenant local time.
terrellt: I need to write PST time to the database as PST time for one tenant, and EST time to database as EST time for another, and foo for foo. It's legacy data, and AR wants to convert to UTC or Local
terrellt: you assume wrong, it's in a "customizations" table per tenant. Legacy data. Horrible legacy data.