search

yodeski / dapper-dot-net

Automatically exported from code.google.com/p/dapper-dot-net
Other
0 stars 0 forks source link

Add special support for the JSV format #144

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
A cool feature to have in dapper would be native support for the JSV-format 
found in ormlite. This might be conflict of interest
considering the current design philosophy of dapper but it would solve trivial 
problems where you have simple associations between multiple models.

Say you have have two models: User and UserSettings. You create two seperate 
database tables and you coerce the data using multi-mapping. But if your design 
architecture contains lots of decoupled models (simple associations) this 
strategy becomes tedious work. Also determining which
model associations might be difficult as the product matures.

Instead you would simply introduce a new 'Jsv' attribute and
dapper would treat the column data as serialized jsv data stored in the 
database. So if you execute a Get, Insert or Update operation you would simply 
serialize/deserialize accordingly.

Both ServiceStack.Text (jsv serializer) and dapper are license compatible so it 
would not be a huge effort implementing this feature.

Original issue reported on code.google.com by peter.su...@gmail.com on 4 Jul 2013 at 1:11

GoogleCodeExporter commented 9 years ago 
In that scenario, why would you not simply use orm-lite? Is there some specific 
feature that makes dapper particularly useful here? I'm *open* to such things, 
but only if I understand the problem first. I'm not sure I do (yet).

Original comment by marc.gravell on 4 Jul 2013 at 6:25

GoogleCodeExporter commented 9 years ago

Original comment by marc.gravell on 5 Aug 2014 at 3:58