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

Accept geomcollection as alias for geometrycollection #10641

Merged
merged 1 commit into from
Jul 7, 2022

Conversation

dbussink
Copy link
Contributor

@dbussink dbussink commented Jul 6, 2022

https://dev.mysql.com/doc/refman/8.0/en/spatial-type-overview.html does not mention geomcollection as an alias, but
https://dev.mysql.com/doc/refman/8.0/en/gis-class-geometrycollection.html
does describe it and it even mentions it as preferred.

This preference shows in SHOW CREATE TABLE statements where geomcollection is always used as the type. We need to be able to parse that for schemadiff then.

In a follow up we can add normalization of this to schemadiff which seems like a better place to match the preference then that MySQL has than in the parser which accepts now both tokens.

Related Issue(s)

#10203

Checklist

  • "Backport me!" label has been added if this change should be backported
  • Tests were added or are not required
  • Documentation was added or is not required

https://dev.mysql.com/doc/refman/8.0/en/spatial-type-overview.html does
not mention `geomcollection` as an alias, but
https://dev.mysql.com/doc/refman/8.0/en/gis-class-geometrycollection.html
does describe it and it even mentions it as preferred.

This preference shows in `SHOW CREATE TABLE` statements where
`geomcollection` is always used as the type. We need to be able to parse
that for `schemadiff` then.

In a follow up we can add normalization of this to `schemadiff` which
seems like a better place to match the preference then that MySQL has
than in the parser which accepts now both tokens.

Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com>
@dbussink dbussink added Type: Enhancement Logical improvement (somewhere between a bug and feature) Component: Query Serving release notes labels Jul 6, 2022
@vitess-bot
Copy link
Contributor

vitess-bot bot commented Jul 6, 2022

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • If this is a change that users need to know about, please apply the release notes (needs details) label so that merging is blocked unless the summary release notes document is included.
  • If a new flag is being introduced, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive.
  • If a workflow is added or modified, each items in Jobs should be named in order to mark it as required. If the workflow should be required, the GitHub Admin should be notified.

Bug fixes

  • There should be at least one unit or end-to-end test.
  • The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

Non-trivial changes

  • There should be some code comments as to why things are implemented the way they are.

New/Existing features

  • Should be documented, either by modifying the existing documentation or creating new documentation.
  • New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • vtctl command output order should be stable and awk-able.

Copy link
Member

@GuptaManan100 GuptaManan100 left a comment

Choose a reason for hiding this comment

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

LGTM!

@GuptaManan100 GuptaManan100 merged commit eeb2016 into vitessio:main Jul 7, 2022
@dbussink dbussink deleted the accept-geomcollection-alias branch July 7, 2022 05:13
rsajwani pushed a commit to planetscale/vitess that referenced this pull request Aug 1, 2022
vitessio#807)

https://dev.mysql.com/doc/refman/8.0/en/spatial-type-overview.html does
not mention `geomcollection` as an alias, but
https://dev.mysql.com/doc/refman/8.0/en/gis-class-geometrycollection.html
does describe it and it even mentions it as preferred.

This preference shows in `SHOW CREATE TABLE` statements where
`geomcollection` is always used as the type. We need to be able to parse
that for `schemadiff` then.

In a follow up we can add normalization of this to `schemadiff` which
seems like a better place to match the preference then that MySQL has
than in the parser which accepts now both tokens.

Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com>
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Query Serving Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants