Skip to content

feat(database): use different integer types declaration with mysql and postgresql according to field length#1978

Open
DevPandi wants to merge 5 commits intotempestphp:3.xfrom
DevPandi:3.x
Open

feat(database): use different integer types declaration with mysql and postgresql according to field length#1978
DevPandi wants to merge 5 commits intotempestphp:3.xfrom
DevPandi:3.x

Conversation

@DevPandi
Copy link

Extends #1972

SQLite: "INTEGER. The value is a signed integer, stored in 0, 1, 2, 3, 4, 6, or 8 bytes depending on the magnitude of the value."

PostgreSQL supports SMALLINT, INTEGER and BIGINT.

MySQL supporty TINY*, SMALL*, MEDIUM*, INTEGER and BITINT.

For simplicity's sake: SMALLINT, INTEGER, BIGINT. Less code, less complexity.

I also picked up on the ideas from the suggestion for text types.

…bytes), integer (4 bytes) and smallint (2 bytes). Tiny INT is SQL.
Comment on lines 21 to 24
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test is empty, is that intentional ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, it was more due to my exhaustion that I didn't reset the file and only noticed it yesterday evening, so to speak. I sat down in the evening and just did it to get back into development even better. Sorry about that. But I won't really get around to it before Sunday because I have a lot of other things to do. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments