[NFR] DB - Data Mapper Implementation

[niden]

Introduce the Data Mapper pattern for the ORM

https://martinfowler.com/eaaCatalog/dataMapper.html

The implementation is based/influenced by Atlas ORM

Related: phalcon/cphalcon#13022

Subtasks:

• [NFR]: Data Mapper: Connection [NFR]: Data Mapper: Connection cphalcon#14733
• [NFR]: Data Mapper: Query [NFR]: Data Mapper: Query cphalcon#14734
• [NFR]: Data Mapper: Table gateway [NFR]: Data Mapper: Table gateway #180
• [NFR]: Data Mapper: Info/Schema [NFR]: Data Mapper: Info/Schema #181
• [NFR]: Data Mapper: CLI scripts for class generation [NFR]: Data Mapper - CLI class generation #580
• [NFR]: Data Mapper: Mapper [NFR]: Data Mapper: Mapper #581
• [NFR]: Data Mapper: ORM [NFR]: Data Mapper: ORM #182
• [NFR]: Documentation Document DataMapper\Query documentation#29
• [NFR]: Query Documentation Document DataMapper\Query documentation#29
• [NFR]: Table Documentation Document DataMapper\Table documentation#243
• [NFR]: Info Documentation Document DataMapper\Info documentation#244
• [NFR]: Cli Documentation Document DataMapper\Cli documentation#245
• [NFR]: Mapper Documentation Document DataMapper\Mapper documentation#246
• [NFR]: ORM Documentation Document DataMapper\ORM documentation#247

[gnumoksha]

Do you have a roadmap for that? I can help with the planning and code.

At the moment I'm creating a Proof of Concept using the current Phalcon Active Record Models to manage a Plain Old PHP Object (POPO). It is very simple but can be a good start point.

[niden]

@gnumoksha This will be in the 4.1 release maybe later depending on how much work we have. We might even release it in stages - not fully functional. For instance we can start by releasing the Table/Row classes first, then the mapper and then tie everything together. Not 100% sure since I have not started it.

Any help will be more than welcome.