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 commento) (1 reazione) (1 assegnatario)Go (6186 fork)batch import

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

Metriche repository

Star: (40.090 star)
Metriche merge PR: (Merge medio 14g 4h) (346 PR mergiate in 30 g)

Descrizione

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

Guida contributor

Direzione di ricerca: Scegli uno dei sotto problemi aperti (ad es. #9796, #9815, #17785) e assicurati che il comportamento corrisponda a MySQL 8.0. Inizia leggendo il problema collegato e riproducendo il bug.
Tech stack: go
Dominio: backend
Tipo issue: Bug
Difficoltà: 2
Tempo stimato: Mezza giornata
Stato attività: Attiva
Chiarezza: Abbastanza chiara
Prerequisiti: SQL
Adatta ai principianti: 50