Size restrictions for string/int types #9
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Research
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#32 Add Unsigned interface
slendium/ocd
Reference
slendium/ocd#9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently databases have to declare
stringandinttypes using the maximum size available to them.The
String_andInt_types should be made public, be declarable as attributes, and introduce a "max length" property. TheString_type should enforce a default max length (breaking change!) and also keep supporting infinite length (use theINFconstant, since it is clearer than having a0sentinel value).The
Schemaclass should be changed to accomodate types being declared as attributes, which override the PHP-declared type.The same should be done for the
Blobtype, if #7 is implemented by then.Update:
Separate the namespaces:
Slendium\Ocd\Schema\Typescontains type implementations andSlendium\Ocd\Schema\Typecontains additional interfaces for types to optionally support.An interface
Type\Sizedwould be implemented by the string and int types.