4 ms·
We're going to do a longer blog post on this later, but if you don't want to use Massive for your sql mapper, maybe try out: http://github.com/clotheshorse/des
by bigdubs 13y ago
We're going to do a longer blog post on this later, but if you don't want to use Massive for your sql mapper, maybe try out:
http://github.com/clotheshorse/destrier http://github.com/clotheshorse/destrier
works similarly in that you can map output to POCOs, but will also let you do more complex querying and CrUD operations.
- joshuaellinger 13y agoLooks interesting. Are you going to build an editor/generator for VS?
- bigdubs 13y agoYes, it's in the roadmap (done through T4).
- Griever 13y agoCool! Impressive that it's even faster than Dapper, too. Personally I'm a huge fan of Dapper but I really like how this is looking. I'll definitely be giving this a shot at some point.
- bigdubs 13y agoHuge caveat; it's only faster than Dapper after the 1st query when it's built up the cached metadata, and only if you're not using referenced objects or child collections. The speed comes from dynamically emiting IL for the object population methods.
- Griever 13y agoAhhh gotcha. Still though, very cool looking project! Having the option to do LINQ-style queries would be nice. I find that Dapper Rainbow rarely satisfies my needs outside of basic CRUD operations.
- cmircea 13y agoHow about PetaPoco?
- bigdubs 13y agoPetaPoco is awesome and I tested against it for performance (it's a little bit faster). Some things this has that PetaPoco doesn't are expression visitors for the where clauses and the concept of referenced objects or child collections.