[RFC]: DDL column classes for ENUM, SET and the remaining MySQL column types
I maintainer di solito rispondono entro 1 giorno
@simon-mundy ci sta già lavorando.
Dal 4/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Proposed Version
0.6.0
Basic Information
Currently Sql\Ddl\Column has 22 classes (the Laminas set plus Double, Json and SmallInteger from #138) and no way to express anything else. Column::$type is protected with no setter and no constructor argument (Column.php#L31, #L33-L38), so the only way to get an ENUM, SET, TINYINT, MEDIUMINT, BIT, YEAR, sized TEXT/BLOB or spatial column is to subclass. This proposal adds those classes, with ENUM/SET values emitted as Argument\Value so nothing caller-supplied reaches SQL as a literal, and fixes Text/Blob silently dropping their length.
Background
The read side is already ahead of the write side. PhpDb\Mysql\Metadata\Source parses enum(...)/set(...) into erratas['permitted_values'] (Source.php#L92-L103) and the enum path is integration-tested against the test_enum fixture (there is no SET fixture in mysql.sql). Nothing consumes permitted_values, and nothing can turn it back into DDL.
Text and Blob override $specification to %s %s (Text.php#L9-L11, Blob.php#L9-L12), so new Text('t', 100) renders TEXT and MySQL's TEXT(n) size selection is unreachable.
The phpdb-mysql-ddl-overrides branch on simon-mundy/phpdb-mysql already has Enum, Set, TinyInteger, MediumInteger, Bit, Year, the sized Text/Blob variants and all eight spatial types — in the adapter namespace PhpDb\Mysql\Sql\Ddl. It is 69 commits behind 0.5.x, pinned to a core branch that no longer exists, and predates the literal-slot rule (Enum quotes values with "'" . $v . "'" and no escaping). Useful for the design and the tests; not something to rebase.
Considerations
- Core or adapter — that is the real question. Core already hosts
Jsonand the MySQL-flavouredON UPDATE CURRENT_TIMESTAMPinAbstractTimestampColumn, so I have assumed core here with the adapter rendering onlySRID. The fork branch went the other way. - The sized Text/Blob variants must suppress the length entirely: MySQL rejects
TINYTEXT(100),MEDIUMBLOB(100)andLONGTEXT(10)with 1064. Column::setOption()is typedbool|string, so until it is widened (#169, also raised in phpdb-mysql#81) an int SRID goes through the constructor$optionsarray or as a string.- Clean rendering depends on the
AbstractLengthColumnValueError fix and theIntegerlength-position fix (#176 and #178). - Every rendering below (
YEAR NOT NULL,BIT(1),ENUM('a', 'b'),POINT SRID 4326) has been executed on MySQL 8.4.10 (reproduced on 8.0.46). - MariaDB and decorator work beyond
SRIDare out of scope.
Proposal(s)
In this order:
EnumandSet. Constructor(string $name, array $values, bool $nullable = false, string|int|float|bool|Literal|Value|null $default = null, array $options = []). Spec%s %s(%s, %s, ...)with oneArgument\Valueper member, so every value is quoted by the platform. Empty$valuesthrowsInvalidArgumentException.TinyInteger(TINYINT) andMediumInteger(MEDIUMINT) extendingInteger, same asSmallInteger.Bit(BIT(M)) extendingAbstractLengthColumn;Year(YEAR, no width —YEAR(4)is deprecated from 8.0.19).TinyText,MediumText,LongTextextendingText;TinyBlob,MediumBlob,LongBlobextendingBlob.Text/Blobthemselves either honour the length (TEXT(n),BLOB(n)) or reject it — the silent drop goes. The sized variants never emit a length.- Spatial:
Geometry,Point,LineString,Polygon,MultiPoint,MultiLineString,MultiPolygon,GeometryCollection, with ansridoption.SRID nis MySQL syntax (8.0.3+), so rendering it belongs in the MySQL decorator; core only carries the option.
Test plan:
new Enum('status', ['active', 'inactive'])renders`status` ENUM('active', 'inactive') NOT NULLon the MySQL platform with each value going throughquoteValue();SetrendersSET(...)the same way.- Every new class gets a unit test in
test/unit/Sql/Ddl/Column/asserting the rendered SQL string, not justgetExpressionData()containment. Text/Bloblength handling is explicit and tested; the sized variants never emit a length.- Round trip: the
test_enumfixture read through the metadataSource(coreAbstractSource::getColumn(), values viaColumnObject::getErrata('permitted_values')) can be re-expressed as anEnumwith the same values — integration test in phpdb-mysql. Add atest_setfixture and do the same forSet. - No new class emits a caller-supplied string as an
Argument\Literal.
Appendix/Additional Info
- #92 (parent), #91 (backed enums), #138 (previous DDL additions).
- From an internal DDL audit (not published — the findings are reproduced above).
- Lingua principale
- PHP
- Stelle
- 18
- Fork
- 8
- Merge medio
- 6g 11h
- PR unite (30g)
- 14
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di php-db/phpdb
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
RFC
Difficoltà 3/5 1-2 giorni Idoneità per principianti 66/100
I maintainer di solito rispondono entro 1 giorno
-
RFC
Difficoltà 5/5 Più di una settimana Idoneità per principianti 38/100
I maintainer di solito rispondono entro 1 giorno
-
RFC
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
RFC
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di php-db/phpdb
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 69/100
PrestaShop/PrestaShop#43140 ·
I maintainer di solito rispondono entro 1 giorno
-
sync-en
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
sync-en
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
I maintainer di solito rispondono entro 3 giorni
-
[Bug] Report tables drop a metric's trailing zeros and cap it at two decimalsForse già presa @lansow l’ha presa oggi. ApertaPotential Bug triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
matomo-org/matomo#25474 ·
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
coollabsio/shoutrrr#190 ·