Enhancement: Consider Mapping class

[guy-lud]

Hello,
I wonder if it's possible to add mapping class like DapperExtensions or Nhibernate has?
Or i could start doing that but i do want to know if the feature will be merge.

IMO i don't like attributes on data objects (entities or dto). so by creating ClassMap<T> it allows us to decoupled the entity from the ORM.

Please advice

[mikependon]

Hi @guy-lud ,

Thank you for this request. Of course that is very possible. I am now considering this already, and might be available on the next minor version (1.11.0).

This is related to the existing request (#399).

[mikependon]

FYI: Please consider sharing the desired syntax you'd like so I can consider it during the implementation.

[mikependon]

@sellig - can you join the discussion here?

@guy-lud, if you have the idea on how to do this, then please do share your class (I will make sure to cover it with the Unit/Integration Tests).

Actually, there is already TypeMapper class where the name is also meant for the purpose. But the implementation is for different mapping purpose (between the .NET CLR Type and DbType). If I am to introduce a new one, I would like to covert both Class and Property mappings (and the name ClassMap<T> invalidates the purpose). Thinking about ClassMapper is only for class mappings and PropertyMapper is only for the properties (ClassProperty, Linq Expression, Field, etc). What do you think?

[sellig]

Hi Michael
Have you already implement something ?

[mikependon]

@sellig - yes, but not yet released. The property mapper is still on going as I am stucked at Linq Expression. Can you be able to test if I am going to release a beta for this?

[sellig]

Yes of course, on my current project, I can test the alternative for

[Map("[schema].[TabelName]")]
[Primary]
[Identity]

attribute

[sellig]

Do you implement a Fluent Interface to do it as suggested in #399 ?

[mikependon]

That is the intention in the end. For now, what I had implemented are these classes.

TBH, some of them are still under development.

• ClassMapper
• PropertyMapper
• TypeMapper
• PrimaryMapper
• IdentityMapper
• PropertyTypeHandlerMapper
• PropertyHandlerMapper

They were implemented as static class mappers. To use it, you have to call each one by one for now.

The fluent mapper like you mentioned will be implemented on top of these classes. I hope that clear up the things.

[sellig]

A fluent interface to replace some Query methods will be also more user readable & userfriendly,

Delete.Table("[schema].[tabelname]")
         .Where(new { VehicleId = vehicle.Id, Category = AssociatedEntitiesCategories.PublicSupport })
         .WithTransaction( _sqlConnectionFactory.Transaction)

Query.Table("[schema].[tabelname]")
         .Top(10)
         .Fields(Field.From("Id", "Name"))
         .Where(searchFields)
        .Orderby(OrderField.Parse(new { Name = Order.Ascending }))

instead of ( abit awfull with all the parameters that can be null)

.Delete( tableName:"[fund].[Vehicle_AssociatedEntities]",
                new { VehicleId = vehicle.Id, Category = AssociatedEntitiesCategories.PublicSupport },
                null,
                null,
                transaction: _sqlConnectionFactory.Transaction

Query(tableName:"[schema].[tabelname]",
       where: searchFields,      
       fields: Field.From("Id", "Name"),
       OrderField.Parse(new { Name = Order.Ascending }),
       top:10)

[guy-lud]

Hi @mikependon,
Thank you for responding so quickly, i really appreciate it.
Long long time ago (when i had fewer children) i forked DapperExtensions and completely changed it to suite my needs.
Maybe the ClassMap<T> code might help?