Having conventions in your POCO objects drive database design and migration? Very cool and very ambitious. I'm interested in seeing where this will go once you start support edge cases (multiple foreign keys, many-to-many associations, etc.). Or is the goal of the SimpleRepository to only be used for barebones CRUD applications? If so, will it play nice with the rest of the system? The automatic migrations seem like they might be more of a headache than a timesaver if the SimpleRepository had to be used in conjunction with normal SubSonic database access.