Everybody is just writing about negative issues so let’s stress some positive issues. Errr, the only positive issue – less (in some cases much less) typing. I wrote GpFluentXMLBuilder just because I hate typing tons of code while creating XML documents. Nothing more and nothing less. The good point with fluent interfaces is that you … Read more
For EF5 and older: In the DbContext.OnModelCreating override for your context: modelBuilder.Entity<Product>().Ignore(p => p.AddressDetails.Country); For EF6: You’re out of luck. See Mrchief’s answer.
You can do a thing like this : [NotMapped] public double[] Data { get { string[] tab = this.InternalData.Split(‘,’); return new double[] { double.Parse(tab[0]), double.Parse(tab[1]) }; } set { this.InternalData = string.Format(“{0},{1}”, value[0], value[1]); } } [EditorBrowsable(EditorBrowsableState.Never)] public string InternalData { get; set; }
Your code is fundamentally an unsafe use of Generics. For example, if I write a new class which extends message, say Threat, and has a new method doSomething(), and then I create a message parameterised by this new class and it creates an instance of Message, and then attempts to Cast it to its subclass. … Read more
The core idea behind building a fluent interface is one of readability – someone reading the code should be able to understand what is being achieved without having to dig into the implementation to clarify details. In modern OO languages such as C#, VB.NET and Java, method chaining is one way that this is achieved, … Read more
The following Python lines should be equivalent to what you have (assuming func, or lambda in your code, returns a Boolean): # Any contains = any(func(x) for x in enumerable) # Count count = sum(func(x) for x in enumerable) # Distinct: since we are using a custom comparer here, we need a loop to keep … Read more
You want to declare T as extends AbstractBuilder<T> in AbstractBuilder. Use an abstract protected method to get this of type T. abstract class AbstractBuilder<T extends AbstractBuilder<T>> { protected abstract T getThis(); public T foo() { // set some property return getThis(); } } class TheBuilder extends AbstractBuilder<TheBuilder> { @Override protected TheBuilder getThis() { return this; … Read more
You need to delete the ItemTypeItem. It is not possible to just remove it from the Items list as it cannot exist by itself, because it has a non-nullable foreign key referencing ItemType (ItemTypeID). To delete the ItemTypeItem add context.Entry(itemTypeItem).State = EntityState.Deleted;
NOTE: Relevant to EF 6 You can use IndexAttribute as mentioned but with Fluent API instead of DataAnnotations which will do the trick: modelBuilder .Entity<Person>() .Property(t => t.Name) .HasColumnAnnotation( “Index”, new IndexAnnotation(new IndexAttribute(“IX_Name”) { IsUnique = true })); Unfortunately there is no other way to create unique indexes using Fluent API. There is an open … Read more
The single biggest challenge I have experienced as a consumer of fluent interfaces is that most of them aren’t really fluent intefaces — instead they are really instances of what I tend to refer to as ‘legible interfaces’. A fluent interface implies that its primary goal is to make it easy to SPEAK it whereas … Read more