Details
Description
| Field | Type | Null | Key | Default | Extra |
|---|---|---|---|---|---|
| emitente_tipo | enum('f','j') | NO | PRI | f |
include the comment column (maybe others columns?)
| Field | Type | Null | Key | Default | Extra | Comment |
|---|---|---|---|---|---|---|
| emitente_tipo | enum('f','j') | NO | PRI | f | hello! |
Gliffy Diagrams
Attachments
Issue Links
- links to
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
I don't think so. SHOW commands are like easy-to-use aliases for INFORMATION_SCHEMA tables — short to type and return less columns to fit nicely on the screen (with some historical exceptions).
SHOW COLUMNS is good as it is, if we start adding more columns to it, it will be too wide and might start wrapping around in the terminal. Use INFORMATION_SCHEMA.COLUMNS to get column metadata that are not shown by SHOW COLUMNS.