Proposed Version
0.6.0
Basic Information
Provide a mechanism for a component-wide standardisation of constraint naming. Currently 'laminas' is prepended to a constraint name across multiple adapters in the \MetaData\Source. Instead we should enforce this from within PhpDb\Metadata\Source\AbstractSource and allow this to be changed at a global level if desired.
Background
_laminas_ key was hardcoded to the file.
Considerations
Not a huge impact, other than to see that it is legacy.
Proposal(s)
protected string $constraintPrefix = '';
public function setConstraintPrefix(string $prefix): void
{
// Ensure alphanumeric and remove leading/trailing underscore
}
protected function getResolvedConstraintPrefix(): string
{
return '_' . $this->constraintPrefix . '_';
}
### Appendix/Additional Info
_No response_
Proposed Version
0.6.0
Basic Information
Provide a mechanism for a component-wide standardisation of constraint naming. Currently 'laminas' is prepended to a constraint name across multiple adapters in the \MetaData\Source. Instead we should enforce this from within PhpDb\Metadata\Source\AbstractSource and allow this to be changed at a global level if desired.
Background
_laminas_key was hardcoded to the file.Considerations
Not a huge impact, other than to see that it is legacy.
Proposal(s)