[8.x] Add tinyText data type to Blueprint and to available database grammars #36949
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bennett-treptow
changed the title
bennett-treptow
added a commit
to bennett-treptow/docs
that referenced
this pull request
Apr 13, 2021
See PR [#36949](laravel/framework#36949)
taylorotwell
pushed a commit
to laravel/docs
that referenced
this pull request
Apr 13, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
tinytextis a valid MySQL data type that indicates a 255-byte string field, and is easily stubbed with varchar or text fields for the other DBMS's. tinyInteger is lonely! Currently,tinytextis not implemented for use in Blueprint.This PR aims to add the
tinyTextmethod to Blueprint, with the nativetinytextdata type being used for MySQL; SQLite will use atextfield, Postgres will use avarchar(255)field, and SQL Server will use anvarchar(255).This PR only adds new functionality, so it would be backwards compatible since no one would be using
tinyTextin their migrations.This could be helpful to those that wanted native support for the
tinytextdata type in MySQL databases.