Paymentsense Dapper.SimpleSave issues

Paymentsense / Dapper.SimpleSave

Saving of new and updated data using Dapper

MIT License

31 stars 12 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Rats - forgot to remove commented out code.

#18 bartread closed 9 years ago
0
Develop

#17 bartread closed 9 years ago
0
Feature/12 incorrectly inserts existing child rows

#16 bartread closed 9 years ago
0
Improve error logging to include generated script

#15 bartread closed 9 years ago
0
Command generation tests should assert against generated scripts rather than intermediate commands

#14 bartread opened 9 years ago
0
For INSERTs where child is reference data with updateable FK columns UPDATE is done on parent

#13 bartread closed 9 years ago
2
connection.Create( ... ) incorrectly inserts existing related objects

#12 mikehancock closed 9 years ago
4
Shouldn't require [ForeignKeyReference] attribute for one to one relationships with FK on parent

#11 bartread opened 9 years ago
0
Should throw a (useful) exception when a circular reference is detected

#10 bartread opened 9 years ago
0
Fixed #8 - added error logging.

#9 bartread closed 9 years ago
0
Dapper.SimpleSave should log errors

#8 bartread closed 9 years ago
0
Fixes #6 Added SimpleSaveIgnoreAttribute to replace ReadOnlyAttribute…

#7 bartread closed 9 years ago
0
[ReadOnly] is a confusing name for an attribute

#6 bartread closed 9 years ago
1
Collections

#5 bartread closed 9 years ago
0
Dapper.SimpleSave - in 1:N relationships where parent exists INSERTed child rows should have parent row key set

#4 bartread closed 9 years ago
4
Dapper.SimpleSave shouldn't enforce *nullable* primary keys on reference data

#3 bartread opened 9 years ago
0
Consider adding support for referencing non-primary key columns to foreign keys in Dapper.SimpleSave

#2 bartread opened 9 years ago
2
Add support for saving collections of objects

#1 chrisliness closed 9 years ago
1