Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify that a primary key is required #7936 #7939

Merged
merged 1 commit into from
Oct 26, 2024
Merged

Conversation

mehov
Copy link
Contributor

@mehov mehov commented Oct 25, 2024

No description provided.

@mehov mehov changed the title Clarify that a primary key is required Clarify that a primary key is required #7936 Oct 25, 2024
@mehov
Copy link
Contributor Author

mehov commented Oct 25, 2024

#7936

@@ -510,7 +510,7 @@ example above we would need tables for ``articles``, ``tags`` and
``articles_tags``. The ``articles_tags`` table contains the data that links
tags and articles together. The joining table is named after the two tables
involved, separated with an underscore by convention. In its simplest form, this
table consists of ``article_id`` and ``tag_id``.
table consists of ``article_id`` and ``tag_id``, as well as `multiple-column ``PRIMARY KEY`` index <https://dev.mysql.com/doc/refman/8.4/en/create-table.html#idm44961976278224>`_ spanning both of these columns.
Copy link
Member

@ADmad ADmad Oct 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't assume that the reader is using MySQL.

Copy link
Member

@dereuromark dereuromark Oct 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In its simplest form, this table consists of article_id and tag_id as well as the default (primary key) id.

would be more correct either way.

Any multi colum setups are not simple or trivial here IMO.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the link is the problematic part as it is MySQL specific, and seems like a URL that will rot due to the fragment id.

@markstory markstory merged commit 1d7dfe7 into cakephp:5.x Oct 26, 2024
3 checks passed
markstory added a commit that referenced this pull request Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants