Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The search_node_links table schedule definition has descriptions for all of its fields but not for the table itself.
Comment | File | Size | Author |
---|---|---|---|
#17 | 203316e.diff | 1.47 KB | mooffie |
#15 | 203316d.diff | 1.47 KB | mooffie |
#13 | 203316c.diff | 1.46 KB | mooffie |
#10 | 203316.patch | 1.19 KB | douggreen |
#8 | 203316b.diff | 1.55 KB | mooffie |
Comments
Comment #1
douggreen CreditAttribution: douggreen commentedHow's this?
Comment #2
bjaspan CreditAttribution: bjaspan commentedPerfect, thanks. I re-rolled the patch to be from the Drupal root directory, not the modules/search directory; otherwise it is unchanged.
Comment #3
Gábor HojtsyThanks, committed.
Comment #4
mooffie CreditAttribution: mooffie commentedThere's another, minor issue in the doc for this table: the doc for the "type" column says "The {search_dataset}.sid of the searchable item to which the word belongs." But shouldn't this be "The {search_dataset}.type of the ..."?
Another thing: if this table holds nodes, then why is a "type" column necessary? Doesn't it always contain "node"?
Comment #5
douggreen CreditAttribution: douggreen commentedThe search module is quite extensible, and this table can hold types other than nodes. This is why there is a 'type' fields, and this is why the id is a 'sid' instead of a 'nid'. However, nothing in Drupal core (and no contrib modules that I know of) implement anything other than nodes.
Comment #6
douggreen CreditAttribution: douggreen commentedHmm, where do you see that the 'type' column says 'The {search_dataset}.sid...'. Looking at the search.install source (lines 78-83), it looks right to me:
Comment #7
Gábor HojtsyReopen please if it does not look right for you.
Comment #8
mooffie CreditAttribution: mooffie commentedIt's further down. I'm attaching a patch with enough context lines to see it.
The description just given to this table was "stores /nodes/ that link to other nodes." It wasn't "stores /items/ that links to other nodes." So I was asking what the point in the "type" column if this table stored only nodes....
I'm attaching a fix to these two issues (plus a bonus one!):
1. Changed one `{search_dataset}.sid' to `{search_dataset}.type'
2. (that's the bonus!) Changed "to which the word belongs" to "that links to the node". This string was copied from another table but somebody forgot to update it.
3. Changed "Stores nodes that link [,,,]" to "Stores items that link [...]." The term 'item' is a the common term used in this file. (Well. I'd actually prefer "Records items" instead of "Stores items.")
Comment #9
Gábor HojtsyLooked at the changes: the 'search_node_links' description we only added after string freeze above, so it is not out for translators yet. The others are also misleading here, so they need fixing. Oh well.
Comment #10
douggreen CreditAttribution: douggreen commented@mooffie, the rephrasing in point 2 makes it more confusing to me. There might be something confusing with the current language, but I don't think you've found the language that clarifies it.
I've rerolled with just 1 and 3. And I've added "(e.g., nodes)" to the table description.
Comment #11
mooffie CreditAttribution: mooffie commentedThe current language isn't confusing. It's just wrong :-)
"to which the word belongs"
What "word"?
A "word" indeed exists in some other table of this module ...but not in the "search_node_links" table.
(I think it's unnecessary to add "(e.q., nodes)." All other descriptions mentioning "items" don't do it. I believe it's clear enough. Also, you wrote "e.q." instead of "e.g.")
Comment #12
douggreen CreditAttribution: douggreen commentedI'm going to give up on wordsmithing this, and let others (@moofie) do it. I'll just try to point out where the language is incorrect.
Sorry, I tried to write "e.g." - a bad habit. We do use "e.g., node" in the search_dataset.sid description. So I guess, having it there is good enough.
I do think "that links to the node" is also wrong. The sid/type pair refers to the source search item, and the nid refers to the node that it links to. So the sid/type pair should say something like "... of the search item containing the link to the node."
Comment #13
mooffie CreditAttribution: mooffie commentedOops. I can be nitpicky sometimes. Please bear with me.
Hey, you're right! I didn't see this. I apologize for accusing you of commiting a crime ;-)
I still don't like this "e.g.," but I accept your judgment.
I'm attaching the patch.
So what's wrong with "that links to the node"? It answers your description.
I don't get it. Why is "containing the link" more correct than "that links to"?
The description of the table says "Stores items (e.g., nodes) that link to other nodes," and I simply took this "that links to" from there.
Comment #14
douggreen CreditAttribution: douggreen commentedI'm not giving up. This is a minor issue for me, and my time is best used writing code, not documentation. So, I'm going to defer the wordsmithing to our technical writers.
I simply don't think that the English words "the {search_dataset}.type that links to the node" is as descriptive as the English words "the {search_dataset}.type of the search item containing the link to the node". In "the {search_dataset}.type that links to the node" the word "that" is the wrong word. I think that in this context, "that" is an adverb that connotes action upon the noun and predicate (?). But it's not the "type" that links to the node", it's the sid/type pair that links to the node. So, the word "that" just doesn't seem right to me.
We need to get the opinion of a couple other technical writers.
Comment #15
mooffie CreditAttribution: mooffie commentedYou misquoted my sentence. The sentence was actually "The {search_dataset}.type of the searchable item that links to the node."
But I don't mind, I'm attaching a patch with your version.
Comment #16
douggreen CreditAttribution: douggreen commentedI never saw that your's had "of the searchable item." If you just read #8, and don't look at the patch close enough, this subtle difference is missed. I like the words "searchable item" better than "search item."
So, I can RTBC the patch in #8, credit to moofie.
Sorry for the stubbornness.
Comment #17
mooffie CreditAttribution: mooffie commentedAgreed. Here it is.
Comment #18
mooffie CreditAttribution: mooffie commentedAhhm. You mean #17. (It contains your "e.g. node" + "containing the link". It's a good one.)
Comment #19
douggreen CreditAttribution: douggreen commentedI was willing to live without the "e.g.", but since you re-rolled it, sure #17.
Comment #20
Dries CreditAttribution: Dries commentedCommitted to CVS HEAD. Thanks.
Comment #21
(not verified) CreditAttribution: commentedAutomatically closed -- issue fixed for two weeks with no activity.