Shoumeng

King Shoumeng (Chinese: 壽夢, d. 561 BC) was the 19th ruler and first king of the state of Wu in the Spring and Autumn period of Chinese history.

Shoumeng
King of Wu
Reign585 BC - 561 BC
IssueKing Liao of Wu
Zhufan, King of Wu
Yuji, King of Wu
Lord Queyou
Yumei, King of Wu
Lord Jizha
Lord Yanyu
Lord Zhuyung
FatherQu Qi

Background

It was under Shoumeng's reign that Wu first began to interact with the other Spring and Autumn states.

Information about the history of Wu prior to Shoumeng is scarce: the Records of the Grand Historian lists the names of 18 rulers before him, but provides no exact regnal dates or biographical information. As such the only known fact about Shoumeng's father and predecessor is that his name was Quqi.[1]

Biography

Shoumeng ascended the throne in 586 BC and was the first Wu ruler to use the title "king", implying equality in rank to the king of Zhou. In the second year of Shoumeng's reign he forged an alliance with Jin, which provided him with modern weapons and training in exchange for his help against Jin's rival Chu. Wu would repeatedly attack Chu in the coming years, and was itself invaded by Chu in Shoumeng's 16th year.[2]

Shoumeng ruled for 25 years. On his deathbed, he had wanted his fourth and youngest son Jizha to succeed him, but Jizha refused. Thus, Shoumeng devised a succession model where his sons would become kings one after the other, hoping that by the time the turn came to Jizha, he would have changed his mind. However, after Shoumeng's death, Jizha stuck to his refusal for the remainder of his life, with the next king instead being the third brother's son.[3]

gollark: I mean, as far as I can tell there isn't really a faster *and* more storage-efficient way to do search than the inverted-index page_tokens thing.
gollark: ```sqlCREATE TABLE crawl_queue ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, lockTime INTEGER, added INTEGER NOT NULL, referrer TEXT);CREATE TABLE pages ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, rawContent BLOB NOT NULL, rawFormat TEXT NOT NULL, textContent TEXT NOT NULL, updated INTEGER NOT NULL);CREATE TABLE page_tokens ( id INTEGER PRIMARY KEY, page INTEGER NOT NULL REFERENCES pages(id), token TEXT NOT NULL, weight REAL NOT NULL);CREATE TABLE links ( id INTEGER PRIMARY KEY, toURL TEXT NOT NULL, fromURL TEXT NOT NULL, lastSeen INTEGER NOT NULL, UNIQUE (toURL, fromURL))```Here is the database.
gollark: To be fair, the text content field isn't that necessary, as for search it uses the page_tokens table anyway and it can be rebuilt from the HTML if I need it.
gollark: The frequency of every word *must* be stored for quick (O(log n) time or something) search, the raw HTML or at least might be needed if I come up with a better way to weight frequency or something, the links are useful for (future) better search ranking algorithms.
gollark: But I suppose I could drop the text bit, that can be reconstructed later™ and search doesn't really need it.

References
  1. Records of the Grand Historian, chapter 31
  2. Records of the Grand Historian, chapter 31
  3. Records of the Grand Historian, chapter 31
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.