mjw1007

53 ms·

571.
by mjw1007 7y ago
That's a bit like retrieving source code by pretty-printing a minimised form. It's not terrible, but it's not going to be as pleasant as the original source. If you maintain your schema like source code, you can use comments,
572.
by mjw1007 7y ago
I recommend the following broad approach: - Maintain your current SQL schema in one place, using normal version control. - Use that form to set up new development versions and so on. - Also maintain migrations (maybe using a migration tool,
573.
by mjw1007 7y ago
I don't think Rust is even defined by a reference implementation, given that they release a new compiler every six weeks. For many practical purposes I think the closest thing to a language definition is the set of testsuites visible t
574.
by mjw1007 7y ago
The Rust Reference is very far from being complete, or even correct in what it does cover. If I have a question whose answer isn't obvious, it's far more likely that I have to go trawling around in RFCs than that there's an a
575.
by mjw1007 7y ago
This is in fact what I do. I'm agreeing with janpot that a richer model would be pleasant. (In practice, when I've wanted this sort of thing it's been good enough to either install all the functions the client might want to u
576.
by mjw1007 7y ago
For what it's worth, I recommend something based on running `CREATE FUNCTION pg_temp.foo()` once per session (and calling it explicitly as `pg_temp.foo()`).
577.
by mjw1007 7y ago
As far as I'm concerned, that comes squarely under the scope of "doable, but fiddly".
578.
by mjw1007 7y ago
The situation I'm thinking of (and I think janpot is) is where your stored procedure or function isn't intended to be a shared interface, but a part of what is notionally your client's code that you happen to want to run serv
579.
by mjw1007 7y ago
AIUI, Postgres has had transactional DDL from early on, while other DBMSes didn't. That means that different Postgres sessions can see different schemas. So I can easily believe that sharing plans across sessions would have been more d
580.
by mjw1007 7y ago
Sometimes you can, but sometimes you want something that can be called as a function. And there's no PREPARE IF NOT EXISTS, so you either have to track yourself whether you've already done it or grub around in pg_prepared_statemen
581.
by mjw1007 7y ago
If you do it that way, you also end up having to rename your function every time it changes, if it's possible that older clients are still running. And if you're tidy-minded you're going to spend effort building a system for
582.
by mjw1007 7y ago
They have to be managed like the database schema, which tends to involve a lot of ceremony. Coping with different function versions for different client versions can be inconvenient. In cases where you want to run functions on the server fo
583.
by mjw1007 7y ago
I think there's one case where saying a plan won't work is the right thing to do, and trying to "get to yes" will often be a mistake: when you understand what needs to be done, and the (time or money) budget is too small
584.
by mjw1007 7y ago
For you to believe that "Rebasing is the same as lying" is mistaken, it isn't necessary for you to be in the "it's a story" camp: it's only necessary for you to believe that the "it's a story&quo
585.
by mjw1007 7y ago
Right, this is the same idea. The current article seems to believe that this behaviour is in some sense irrational, presumably on the theory that "rationally" you should never prefer to remove a potentially useful option (which af
586.
by mjw1007 7y ago
They did replace Samba with their own SMB stack, and the new one was very buggy indeed, to the extent of "eats your data in normal usage when run against a contemporary Windows server".
587.
by mjw1007 7y ago
I think the switch to black-on-white when GUIs first appeared was largely because the prototypical application was a word processor, where the selling point was that what you saw on the screen looked like what you were going to print on pap
588.
by mjw1007 7y ago
Certainly the student has wronged the university, but to my mind it's the same kind of wrong as if they'd smuggled a calculator in to an arithmetic test. That also lets the student gain a reputation they didn't deserve. I wou
589.
by mjw1007 7y ago
Another annoying thing is that university plagiarism policies seem to have been largely written by humanities departments without thinking very hard about the needs of others. Taken literally, my local university's plagiarism policy sa
590.
by mjw1007 7y ago
I think part of the problem here is that universities have repurposed the word "plagiarism" to include forms of cheating which it doesn't naturally cover. For example, if a student pays someone else to write an essay, nowaday
591.
Google LLC vs. Oracle America Inc(scotusblog.com)
1 points by mjw1007 7y ago|0 comments
592.
by mjw1007 7y ago
Hm, is the secrecy of that URL the only thing stopping someone else downloading the backup?
593.
by mjw1007 7y ago
« Chiang thus argues Musk’s doomsday scenario isn’t a useful tool for thinking critically about the risks AI poses. The thought experiment is poisoned by projection, reflecting a libertarian desire to free corporations from regulatory const
594.
by mjw1007 7y ago
I think the central point here is "completeness must be sacrificed whenever implementation simplicity is jeopardized". Indeed, sometimes omitting a feature which really ought to be there makes life easier for the end user, not jus
595.
by mjw1007 7y ago
I think there are two "axes" here: One is: - A: a list of functions or similar items, vs - B: a description of a model, its operations, and terminology The other is - X: "the only job is to describe, as clearly and completely
596.
by mjw1007 7y ago
It's good advice, but I think that like a lot of such articles it's talking about how to run, when there's a need for more articles on how to walk. That is, the first duty of technical documentation is to be complete and corr
597.
by mjw1007 7y ago
https://www.divio.com/blog/documentation/
598.
by mjw1007 7y ago
Like the "What nobody tells you about documentation" post that was going round recently, this one says that the way to write your "final source of truth" documentation is to document each individual function and assume t
599.
by mjw1007 7y ago
In RFC-world (which may not be the same as the real world), there's no need for `Vary` on a 400 response, because a 400 response isn't cacheable (unless it has a cache-control or expires header).
600.
by mjw1007 7y ago
As far as I know Debian intends to have no plain `python` on the default PATH once the python2 packages are removed, so that it will be up to the system administrator to decide where that will point. See eg https://lists.debian.o

More ›