Proposed Version
0.6.0
Basic Information
In keeping with modern database terminology this RFC proposes to rename the Feature to what is now an industry-standard approach. Over the last few years, most database vendors have moved to neutral, descriptive language that better reflects how replication actually works.
Background
No response
Considerations
No response
Proposal(s)
The existing feature will be marked as deprecated, retaining its name but extending a newer PrimaryReplicaFeature (duplicating existing functionality) and proxying the getSlaveAdapter and getSlaveSql to getReplicaAdapter and getReplicaSql methods, also with deprecation notices.
The MasterSlaveFeature will then look to be removed in the next major release of PhpDb.
Appendix/Additional Info
No response
Proposed Version
0.6.0
Basic Information
In keeping with modern database terminology this RFC proposes to rename the Feature to what is now an industry-standard approach. Over the last few years, most database vendors have moved to neutral, descriptive language that better reflects how replication actually works.
Background
No response
Considerations
No response
Proposal(s)
The existing feature will be marked as deprecated, retaining its name but extending a newer PrimaryReplicaFeature (duplicating existing functionality) and proxying the getSlaveAdapter and getSlaveSql to getReplicaAdapter and getReplicaSql methods, also with deprecation notices.
The MasterSlaveFeature will then look to be removed in the next major release of PhpDb.
Appendix/Additional Info
No response