Updated Wiki: What's new
Whats new in v2.10.2:Case 93. Merge logic for foreignKey column matching, previously .col=null was possible. Thanks toAHewgill.StoredProcs that return nullable binary types generate invalid...
View ArticleClosed Issue: UseCamelCase = false causes "Failed to read database schema" [93]
When I change UseCamelCase from true to false I am getting the following error:```// -----------------------------------------------------------------------------------------// Failed to read database...
View ArticleClosed Issue: Bridge tables schema issue [98]
I have found a bug in EF.Reverse.POCO.Core.ttinclude line 2326 : if prependSchemaName variable is false, the many-to-many configuration method is generated without the schema parameter. It should do...
View ArticleClosed Feature: Add a default for getutcdate() [96]
We use both the getdate() and getutcdate() for our DB. Would it be possible to change the "Validate default" switch statement for the "datetime" to read this:```case "datetime": DateTime dt;...
View ArticleClosed Issue: Missing "using DatabaseGeneratedOption =...
Hello, thanks for your project!There is a missing case "4.5": in EF.Reverse.POCO.ttinclude : Line 64 Thank you.
View ArticleReleased: v2.10.2 (Feb 26, 2015)
Whats new in v2.10.2:Case 93. Merge logic for foreignKey column matching, previously .col=null was possible. Thanks to AHewgill.StoredProcs that return nullable binary types generate invalid...
View ArticleCreated Release: v2.10.2 (Feb 26, 2015)
Whats new in v2.10.2:Case 93. Merge logic for foreignKey column matching, previously .col=null was possible. Thanks to AHewgill.StoredProcs that return nullable binary types generate invalid...
View ArticleEdited Feature: Specify additional using namespaces [99]
According to the info in Database.tt, it should be possible to specify an IdentityDbContext base class. While this is technically true, it's only possible by fully qualifying the namespace...
View ArticleCommented Feature: Specify additional using namespaces [99]
According to the info in Database.tt, it should be possible to specify an IdentityDbContext base class. While this is technically true, it's only possible by fully qualifying the namespace...
View ArticleEdited Feature: Specify additional using namespaces [99]
According to the info in Database.tt, it should be possible to specify an IdentityDbContext base class. While this is technically true, it's only possible by fully qualifying the namespace...
View ArticleCommented Feature: Specify additional using namespaces [99]
According to the info in Database.tt, it should be possible to specify an IdentityDbContext base class. While this is technically true, it's only possible by fully qualifying the namespace...
View ArticleSource code checked in, #72d208eb679c
Case 99. Add ability to specify additional using namespaces. Thanks to rorourke.
View ArticleCommented Feature: Specify additional using namespaces [99]
According to the info in Database.tt, it should be possible to specify an IdentityDbContext base class. While this is technically true, it's only possible by fully qualifying the namespace...
View ArticleSource code checked in, #922898a4a9af
Remove FakeDbContext and FakeDbSet in the unit tests as these are now generated.
View ArticleSource code checked in, #3e561d859fd1
Corrected integration test to point to the northind database.
View ArticleSource code checked in, #3ccb5aee520b
Moved the IRepository and MockRepository into the unit test project
View ArticleUpdated Wiki: What's new
Whats comming in the next version:Case 61. Allow excluding/modifying columns. Also permits you to run a function against each column to optionally modify the column properties (eg. to tweak the name of...
View Article
