为什么大型机白胡子将 DB2/zOS 称为“他”?

发布于 2024-08-29 12:56:56 字数 264 浏览 4 评论 0原文

如果您向 DB2/zOS 引擎 DBA 询问有关 DB2 行为的问题,DBA 会将 DB2 引擎称为“他”,就像水手使用“她”来指代他的船一样。

例如:“一旦填充了可用空间,DB2 仍然希望在表空间中按簇顺序保留这些行。这就是为什么他会将该页分成两半,最终会得到许多半空页。也就是说,除非您刚刚插入的行的簇键是表中最高的,在这种情况下,他会创建一个新的空页,然后将您的新行放入该页中,所以我不必执行此 REORG。如果你按照我的建议对你的输入进行排序。”

有谁知道这个传统从何而来?

If you ask a DB2/zOS engine DBA a question about DB2's behavior, the DBA will refer to the DB2 engine as "he" much the way a sailor uses "she" to refer to his ship.

For example: "Once you fill the freespace, DB2 still wants to keep those rows in cluster order in the tablespace. That's why he'll split that page in half, and you end up with lots of half-empty pages. That is, unless the cluster key of the row you've just inserted is the highest in the table, in which case he makes a new empty page, and he puts just your new row into that page. So I wouldn't have to do this REORG if you would just sort your input like I suggested."

Does anyone know where this tradition comes from?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

旧情勿念 2024-09-05 12:56:56

这当然不是一个固定的话题。 DB2-L 邮件列表上最近对此进行了讨论 Phil Grainger 统计了 100 多个回复,如下所示:

  • 29% 的人说“DB2 是一个它”
  • 25% 的人说“DB2 就是 DB2”
  • 21% 的人说“绝对是一个他”
  • 20% 的人说“DB2 是一个她”
  • 其他5% 声称他们从未想到过这个问题

This is certainly not a settled topic. There was a recent discussion on the DB2-L mailing list on this very topic, and Phil Grainger tallied the over 100 responses like this:

  • 29% said "DB2 is an it"
  • 25% said "DB2 is just DB2"
  • 21% said "Definitely a he"
  • 20% said "DB2 is a she"
  • Other 5% claimed that the question had never occurred to them
因为看清所以看轻 2024-09-05 12:56:56

我就是那些灰胡子之一。我从事大型机工作已经有一段时间了,但我记得这种“个性化”程序的趋势。

这在一定程度上是对程序编写者的认可。但首先,它只是一种语音工具,提醒人们该程序旨在出于特定原因以给定方式工作。

从纯粹的功能角度来说,它通常比将程序描述为没有生命的自动机器更容易(当这种情况发生时,它会做出响应,等等)。

I'm one of those grey beards. It's been a while since I worked on mainframes, but I recall this tendency to 'personalize' the programs.

It is in part an acknowledgement of the person who wrote the program. But primarily, it is just a tool of speech, serving as a reminder that the program is designed to work in a given way, for specific reasons.

And it is generally easier than describing the program as a lifeless autonomatic machine, in pure functional terms ( when this happens, it responds with that, etc ).

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文