[RFC]: Platform Satellite Migration

[tyrsson]

Proposed Version

3.0.0

Basic Information

Migration of "platforms" to satellite packages.

Background

Please see the 3.0.0 scope of work RFC for details.

Considerations

All platform specific code will migrate to target axleus/laminas-db-mysql satellite package. This will of course require a few changes to the core axleus/laminas-db package interfaces/classes. I am currently working out the full scope of these required changes. I will update this RFC as more details are discovered.

Proposal(s)

At a minimum.

• Refactor the Adapter\Adapter to an abstract class
• Implement a concrete Adapter class per platform along
• Migrate all relevant Driver/Platform code to the satellite package
• Introduce factories/delegators to facilitate this migration so the core package can depend on finding its required components when mapped into service manager from the satellite packages ConfigProvider classes.

I will add more concrete requirements here as testing progresses.

Appendix/Additional Info

N/A

[tyrsson]

@settermjd @simon-mundy
So, ideas/suggestions on how to best integrate the documentation for these with the docs for laminas-db? I've never built the doc setup that laminas uses in all of their projects locally so I'm kinda unsure of what the requirements are as far as directory structure etc is.

[tyrsson]

@settermjd @simon-mundy

After giving this A LOT of thought. Here is my suggestions.

1. Make the shift to AdapterInterface typing
2. Split to laminas/laminas-db-adapter-mysql naming
3. Refactor ONLY what is required to migrate the code into the satellite and to remove dead code that the migration introduces. An example of that dead code would be the large switch statements in many of the connection classes. The only package that would need to retain any logic like that would be mysql since it has multiple backing adapters, mysqli, pdo.
4. Skip the introduction of new factories etc so that a intermediate 2.2x.x can be tagged to provide a smoother upgrade path for downstream users.
5. Migrate relevant test to the satellite packages and refactor ONLY what is required to get test passing.
6. Tag the 2.2x.x compatible satellite package releases.
7. Continue this process until all adapters/platforms are migrated to working satellite packages.
8. Tag the laminas-db 2.2x.x release.

-- Update ALL docs.

1. Immediately start work on the 3.0.x branch (which is really just a continuation of current development) Refactor for SMv4 support. Introduce the adapter plugin manager and related delegator and related unit/integration test.
2. Tag release.

-- Write new docs.

[tyrsson]

This issue is being closed as deprecated