This project has moved and is read-only. For the latest updates, please go here.

Tables and columns names by convention

Nov 19, 2013 at 2:55 PM

Thanks for wonderful dapper extension. Only strong typing can save the world! :)

I would like to ask have you though about implementing convention style naming for tables and columns instead of SQLinqTable and SQLinqColumn attributes because why to use not-refactorable strings if we could just use same naming in db?

Best regards
Aug 2, 2014 at 11:51 PM
By default the column name used will be the exact name of the class property. Only if the database field name differs is it necessary to use the SQLinqColumn attribute. The table name is the same as it goes off the class name unless SQLinqTable is specified.
Oct 24, 2014 at 7:50 AM
Hi crpietschmann,

SQLinqColumnAttribute doesn't work in select query result. If query result is a generic object, columns (with property names) values are null. If query is a dynamic object, columns (with db schema names) has values but I can't get values in this case .