Skip to content

Database schema review #211

@cannium

Description

@cannium

@cxt90730 @dahefanteng @thesues

I think DB schema needs some review, for the following reasons:

  • some columns were designed for HBase, and not fit TiDB/MySQL very well
  • we need to support versioning (business pressure)
  • some tables do not have an explicit primary key (WTF!?)
  • intensively use null value (ref)
  • intensively use JSON type (ref)
  • use varchar for enumeration types
  • mysterious names, e.g. multipartpart, multiparts, objectpart

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions