@jmoiron @kaihendry Unfortunately, table names aren't parameterizable; at least not consistently. "The arguments can only be used as data values, not as identifiers", see https://t.co/z64InhY5t4 .. I think this is consistent across many backends.
jmoiron plays the blues
@jmoiron RT @spiffxp: Congrats to a bunch of dudes. You could at least hold yourself to the same standard you expect of panel submissions to your co…
@jmoiron @dgryski @francesc I swap around a lot, sometimes I want to relax and sometimes I want energy... absolute silence + wearing my headphones without any music playing at all is also on heavy rotation
@jmoiron @francesc lofi study girl, citypop, chillwave, futurefunk, chiptunes, anything johnny pate and most funk besides, and most types of jazz (wes montgomery, kenny burrell, django, miles, astrud & joão, ryo fukui, ...)
@jmoiron RT @kaihendry: New video about a little internal @golang tool I made with the help of @jmoiron's SqlX & @MarkusWinand No offset advice. htt…
@jmoiron @elithrar @kisielk @golang I have those too, basically every time I get an email :)
@jmoiron @elithrar @kisielk @golang You and @kisielk have done an incredible job.
@jmoiron RT @pauldix: Announcing the first @InfluxDB 2.0 Alpha Release and the Road Ahead! https://t.co/uAZlJFmDjB. Very excited for the start of ou…
@jmoiron @dgryski @bmizerany NPM et al sure do look an awful lot like a grocery store.
@jmoiron 2.5 years later and I'm not sure we know any better https://t.co/FjKnqZmfSd https://t.co/D3cW3e9kip
@jmoiron @Sajma I'm a big fan of yujacha. It's the perfect weather for it at the moment, too.
@jmoiron @chimeracoder It's very Microsoft.
@jmoiron @davidcrawshaw Being able to 1_000_000 is a nice change for legibility, although where to put _'s won't cross cultures cleanly. I'll probably fail anything using hex floats in code review, assuming they'll ever even crop up.
@jmoiron Finally, hexidecimal floating point https://t.co/dvDtqjHs9Z I was starting to worry that I'd always be able to read numeric literals in my code.
@jmoiron @acoustik @pauldix Timescale's SQL is as good as it gets for timeseries in SQL, but I can't deny that at times it looks like a target language to me :) "... WINDOW w AS (ORDER BY time) ORDER BY 1"
@jmoiron @pauldix Def a big tradeoff. Extensions should compose with existing SQL semantics, and it's tempting to hastily implement "SELECT rate(x) FROM x EVERY 60s" and fail to make that connection. But without extensions simple queries can get very unwieldy, eg https://t.co/4DSNeTVrTV
@jmoiron SQL has been continuously extended since its creation, but this is a pretty common sentiment. I'm still in the "an extension of SQL for doing time range queries w/ aggregations is a good idea" camp... there's a blog post missing on this topic. https://t.co/XykwqBzly2
@jmoiron @wernerdrew you're gonna love "ramble on" now
@jmoiron @wernerdrew are you subtweeting me grandpa
@jmoiron If the documentation for your interface is not easy to write, the interface is probably not easy to use.
@jmoiron @chimeracoder As someone who came to the Beatles much later than Dylan, well into my 20s, my first listens to Beatles albums were full of "Oh, this is theirs?!"
@jmoiron @chimeracoder Joe Cocker's help from my friends is probably the cover that most transcends a Beatles original, a la Hendrix's watchtower. But numerically there are probably a lot of charting Beatles covers out there.
@jmoiron @chimeracoder The Beatles might be close.
@jmoiron @chimeracoder Kraftwerk is a genre, right? Most serious examples I can think of are derivatives (industrial, punk, grunge, probably several dozen overly classified EDM subgenres).
@jmoiron I used to second guess myself with `ln` but someone once told me that it behaves exactly the same as `cp` wrt argument count and order and all at once this was never an issue again. https://t.co/IovNPFCp3a