Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sgarland
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
34 ms
·
571.
▲
by
sgarland
1y ago
This presupposes that the reader likes or even uses auto-complete. I do not, and there are many others like me.
572.
▲
by
sgarland
1y ago
> always creating an intermediary result-set You want the DB to first run SELECT * FROM <table>, and then start operating on that?
573.
▲
by
sgarland
1y ago
The complaints listed seem to focus on attributes / methods of a class. You can read Python’s docs, and see the methods available to a str type, for example. To me, that’s learning the language. Learning its library would be more like
574.
▲
by
sgarland
1y ago
It's written that way because it stems from relational algebra, in which the projection is typically (always?) written first. >The order should be FROM -> SELECT -> WHERE, since SELECT commonly gives names to columns, which WH
575.
▲
by
sgarland
1y ago
Is the entire complaint that autocomplete doesn’t work well? Have you tried learning your language?
576.
▲
by
sgarland
1y ago
Mapping a DB response to a Pydantic model is hardly an ORM.
577.
▲
by
sgarland
1y ago
If you have to change your schema frequently, you didn’t adequately (or at all, more likely) model your data. DB schema is supposed to be inflexible and strict; that’s how you can guarantee that the data it’s storing is correct. > The 90
578.
▲
by
sgarland
1y ago
As the sibling comment mentioned, this is a solved problem. MySQL and MariaDB take a very brief lock on the table at the very end of index creation that you will not notice, I promise. Postgres does the same if you use the CONCURRENTLY op
579.
▲
by
sgarland
1y ago
Because web devs are so used to terrible design, poorly-optimized DB schemas, and networked storage latency that they have no idea what a single server (or indeed, a humdrum desktop) is capable of. Like when I inform teams complaining of “s
580.
▲
by
sgarland
1y ago
Fair point. Unfortunately for me, the only kind of microservice architecture I’ve ever worked with is a distributed monolith - at multiple companies.
581.
▲
by
sgarland
1y ago
Agreed, and I don’t know why you’re being downvoted. If someone told me their virtual circuit breaker “fails open,” I would assume that it stops processing data upon failure.
582.
▲
by
sgarland
1y ago
Two things: 1. Essentially every RDBMS except MySQL has a RETURNING clause, so you can read your write essentially for free (and even MySQL lets you read the auto-increment value it inserted). 2. Barring that, how is this finicky to get rig
583.
▲
by
sgarland
1y ago
Unless all your tables have the same width - or you’re doing weird things with constants in your SELECTs - you can’t UNION the various queries, so they’re sequential. You could parallelize those I suppose, but now you’re adding more compl
584.
▲
by
sgarland
1y ago
> 50 ms p99 You realize that’s abysmally bad performance for any reasonable OLTP query, right? Sub-msec (as measured by the DB, not including RTT etc.) is very achievable, even at scale. 2-3 msec for complex queries.
585.
▲
by
sgarland
1y ago
> Additionally, having five services accessing the same database is a code smell. Counterpoint (assuming by database you mean database cluster, not a schema): having a separate physical DB for each service means that for most places, you
586.
▲
by
sgarland
1y ago
The horror. /s
587.
▲
by
sgarland
1y ago
OpenBSD switched their PRNG to arc4random in 2012 (and then ChaCha20 in 2014); depending on how accurate your time estimate is, that could well have been the cause. Linux switched to ChaCha20 in 2016. Related, I stumbled down a rabbit hole
588.
▲
by
sgarland
1y ago
12-year-old me had (or rather, my family had) a Celeron 333 MHz and a Pentium III 550 MHz, both from Gateway, because that was the sole awesome perk my dad got from working there: literally free computers, with a required number of years of
589.
▲
by
sgarland
1y ago
I read this [0] (I also recommend reading part 1 for background) a few weeks ago, and found it quite interesting. The entire concept of data lakes seems odd to me, as a DBRE. If you want performant OLAP, then get an OLAP DB. If you want tem
590.
▲
by
sgarland
1y ago
Considering a common use for Windows these days is Steam Launcher, performance is kind of a big deal, actually. Literally the only thing I use my desktop for is to play games, so yes, performance is pretty much the only thing I care about w
591.
▲
by
sgarland
1y ago
No, I misunderstood the comment I was replying to, and thought they were assuming they could use /tmp as an un-curated dumping ground that was never deleted. I also am used to it being wiped on boot.
592.
▲
by
sgarland
1y ago
Because the idea of DX was invented, and devs now clutch to it like it’s the last life preserver on a sinking ship. “If you normalize your schema, it will be 20x smaller, and you’ll eliminate an entire class of bugs.” “Hmm, but then we’ll h
593.
▲
by
sgarland
1y ago
They cosplay as architecting them that way. IMO, one of the largest negative consequences to EverythingAsAService is that it allows people with little to no experience administering and tuning systems to run complex pieces of software. Sure
594.
▲
by
sgarland
1y ago
TFA mentions this [0] delightful series of articles, in which it’s calculated that every KB of JS sent to clients cost Kroger $100K/yr. [0]: https://dev.to/tigt/making-the-worlds-fastest-website-and-ot...
595.
▲
by
sgarland
1y ago
I can’t fathom why anyone would be surprised that a directory named “tmp” is ephemeral.
596.
▲
by
sgarland
1y ago
Same. It took me a little bit to get used to it; my initial snap judgment was “this will be more annoying to create via scripting,” but then Ansible added deb822_repository [0] in 2.15 (shortly before Bookworm was released), and then it was
597.
▲
by
sgarland
1y ago
DEB822 was available from at least Buster [0]. I think Bullseye was the first release I used it in. [0]: https://manpages.debian.org/buster/apt/sources.list.5.en.htm...
598.
▲
by
sgarland
1y ago
> We aren't painting sistine chapels, we are running the plumbing in the sistine chapels basement. Sure, but in plumbing - or any trade - there is a huge spectrum of quality of work. Tons of little details add up that confer the per
599.
▲
by
sgarland
1y ago
I also interviewed with them a couple of years ago, for their Database SRE (AKA DBRE) role. It was going quite well until I discovered that they required you to live within commuting distance of an office, and unfortunately I had just mov
600.
▲
by
sgarland
1y ago
Or you rewrite queries on the fly with ProxySQL or similar to use the new column name, and then deploy the new code. Can even insert a momentary pause at the proxy layer so no queries hitting the old name sneak through while you do the rena
More ›