No support for MySQL enum and float field type?
See original GitHub issueFollowing #51, I found that MySQL enum and floar fields are simply ignored by Forest and not displayed at all.
We have the following field in our DB model which works and displays just fine using Sequelize:
status: {
type: DataTypes.ENUM,
values: ['pending', 'listed'],
allowNull: false,
defaultValue: 'pending'
},
display_order: {
type: DataTypes.FLOAT
}
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
MySQL 8.0 Reference Manual :: 11.3.5 The ENUM Type
An ENUM is a string object with a value chosen from a list of permitted values that are enumerated explicitly in the column...
Read more >11.1.4 Floating-Point Types (Approximate Value)
The FLOAT and DOUBLE types represent approximate numeric data values. MySQL uses four bytes for single-precision values and eight bytes for double-precision ...
Read more >MySQL 8.0 Reference Manual :: 11 Data Types
MySQL supports SQL data types in several categories: numeric types, date and time types, string (character and byte) types, spatial types, and the...
Read more >11.7 Data Type Storage Requirements
This section includes guidelines and information for the storage requirements for each data type supported by MySQL, including the internal format and size ......
Read more >11.1.1 Numeric Data Type Syntax - MySQL :: Developer Zone
As of MySQL 8.0.17, the UNSIGNED attribute is deprecated for columns of type FLOAT , DOUBLE , and DECIMAL (and any synonyms); you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Manual changes are a workaround but definitely not a fix. This issue should be reopened.
Hi, I am facing the same issue. How can I fix it ? Thanks