Low code platform for building business apps and workflows in minutes. Supports PostgreSQL, MySQL, MariaDB, MSSQL, MongoDB, Rest API, Docker, K8s, and more 🚀
Describe the bug
When a SQL Server table with field of type "tinyint" is imported, it is interpreted as a boolean value and the interface does not let you to change the data type.
To Reproduce
Steps to reproduce the behavior:
Create a table with a tinyint field in sql server, add a few values
Import table and see the table with all values check.
Expected behavior
The field should be integer number
Screenshots
The screenshots are above.
Additional context
For some reason the exported schema shows table with duplicated columns:
CREATE TABLE [TB_TesoreriaTipo] (
TipoID tinyint(1) NOT NULL,
TipoID tinyint(1) NOT NULL,
Tipo varchar(100) NULL,
Tipo varchar(100) NULL,
CONSTRAINT [PK_TB_TesoreriaTipo] PRIMARY KEY (TipoID)
);
Checklist
Hosting
Describe the bug When a SQL Server table with field of type "tinyint" is imported, it is interpreted as a boolean value and the interface does not let you to change the data type.
To Reproduce Steps to reproduce the behavior:
Expected behavior The field should be integer number
Screenshots The screenshots are above.
Additional context
For some reason the exported schema shows table with duplicated columns: