Moving on from Rails, and what's next https://blog.seantheprogrammer.com/moving-on-from-rails-and-whats-next …
Show this thread
-
Some types (e.g. integer) should be getting handled by the PG gem already. I know the reason we couldn't have dates happen there is because its behavior differed from AR too much. A bigger win would be getting binary transmission for date(time)?, but... 1/2
Good luck with Crates!
libpq doesn't support per-column binary/text specification (we don't want binary for types like Array in Rails), even though it's supported by the protocol so the native driver for the adapter would need to work at the TCP level rather than being based on libpq. 2/3
-
-
I've been working on and off on a new async postgresql adapter for Diesel which would be able to handle that and was hoping to use that for Rails, but that has stalled from async in Rust not being where I needed it to for the API I wanted for Diesel 3/4
-
Anyway my point is that timestamp columns are by far the most expensive to deal with (the second being the allocation of the Ruby string object but that shouldn't be a thing for integer any more at least), and having binary transmission for that is a way bigger win than C vs Ruby
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.