Bugs / compatibility issues of view · pingcap/tidb#9798

2019-03-19T05:09:02.000Z

## Description - [ ] https://github.com/pingcap/tidb/issues/9796 Create view with INSERT only privilege behaves different with MySQL 8.0 - [x] https://github.com/pingcap/tidb/issues/9788 Column name should be expanded when creating the view. - [ ] https://github.com/pingcap/tidb/issues/9815 ALTER VIEW not supported - [x] https://github.com/pingcap/tidb/issues/9875 EXPLAIN Select * from view requires different privileges to MySQL - [x] https://github.com/pingcap/tidb/issues/9893 mysql.tables_priv does not support view related privileges -> [WIP] https://github.com/pingcap/tidb/pull/9894 - [ ] https://github.com/pingcap/tidb/issues/17785 Views do not support column elimination - [x] https://github.com/pingcap/tidb/issues/9816 can't drop view ## SIG slack channel [#sig-exec](https://tidbcommunity.slack.com/archives/CMRD79DRR) ## Score - 300 ## Mentor * @SunRunAway

(1 Kommentar) (1 Reaktion) (1 zugewiesene Person)Go (6.186 Forks)batch import

challenge-programhelp wantedpriority/P3sig/executiontype/compatibilitytype/new-feature

Repository-Metriken

Stars: (40.090 Stars)
PR-Merge-Metriken: (Durchschn. Merge 14T 4h) (346 gemergte PRs in 30 T)

Beschreibung

Description

https://github.com/pingcap/tidb/issues/9796 Create view with INSERT only privilege behaves different with MySQL 8.0
https://github.com/pingcap/tidb/issues/9788 Column name should be expanded when creating the view.
https://github.com/pingcap/tidb/issues/9815 ALTER VIEW not supported
https://github.com/pingcap/tidb/issues/9875 EXPLAIN Select * from view requires different privileges to MySQL
https://github.com/pingcap/tidb/issues/9893 mysql.tables_priv does not support view related privileges -> [WIP] https://github.com/pingcap/tidb/pull/9894
https://github.com/pingcap/tidb/issues/17785 Views do not support column elimination
https://github.com/pingcap/tidb/issues/9816 can't drop view

SIG slack channel

#sig-exec

Score

Mentor

@SunRunAway

Contributor Guide

Research-Richtung: Wählen Sie eines der offenen Unterprobleme (z.B. #9796, #9815, #17785) und stellen Sie sicher, dass das Verhalten mit MySQL 8.0 übereinstimmt. Lesen Sie zunächst das verknüpfte Problem und reproduzieren Sie den Fehler.
Tech Stack: go
Domain: backend
Issue Type: Fehler
Schwierigkeit: 2
Geschätzte Zeit: Halber Tag
Aktivitätsstatus: Aktiv
Klarheit: Meist klar
Voraussetzungen: SQL
Einsteigerfreundlichkeit: 50