For me STE is absolutely wrong concept. It is just another implementation of DataSet. In ASP.NET application you will have to store STEs somewhere among requests. In first request you will query your datasource to get STE and provide data in the page. In the next request (postback) you will want to modify STE with … Read more
I’ve got interesting performance testing results and I’ve found a culprit. I have not seen any information like this in any EF source I’ve ever read. It turns out to be Equals overridden in a base class. The base class supposed to contain Id property shared between all types of concrete entities. This approach recommended … Read more
Instead of calling them POCOs, I prefer to call them persistence ignorant objects. Because their job is simple, they don’t need to care about what they are being used for or how they are being used. Personally I think POCOs are just another buzzword (like Web 2.0 – don’t get me started on that) for … Read more
for future reference: you can use data annotations MSDN EF – Code First Data Annotations [NotMapped] public string AddressAs { get; set; }
POCO stands for “Plain Old C# Object” or “Plain Old CLR Object”, depending on who you ask. If a framework or API states that it operates on POCO’s, it means it allows you to define your object model idiomatically without having to make your objects inherit from specific base classes. Generally speaking, frameworks that work … Read more
The reason for the error are incorrectly configured relations in your model. This is not correct: one.HasRequired(t => t.Two) .WithMany(s => s.Ones) .HasForeignKey(t => t.TwoId); one.HasRequired(t => t.Three) .WithMany(s => s.Ones) .HasForeignKey(t => t.ThreeId); It should be: one.HasRequired(t => t.Two) .WithMany(s => s.Ones) .HasForeignKey(t => new { t.TwoId, t.ThreeId }); Because dependent’s FK must contain … Read more
When you insert an object, if it doesn’t have an _id field then the driver adds one and sets it to a 12-byte MongoDB ObjectId value. You just need to add an Id property to your POCO, which will be deserialised from _id: public class Thingy { public ObjectId Id { get; set; } } … Read more
You cannot achieve it directly because neither eager or lazy loading in EF supports ordering or filtering. Your options are: Sort data in your application after you load them from database Execute separate query to load child records. Once you use separate query you can use OrderBy The second option can be used with explicit … Read more
This answer comes ‘a bit’ late as I’ve just faced the same issue with EF4 POCO proxies. I solved it using a custom converter that calls Mapper.DynamicMap<TDestination>(object source) to invoke the runtime type conversion, rather than the .Include<TOtherSource, TOtherDestinatio>(). It works fine for me. In your case you would define the following converter: class PaymentConverter … Read more
Actually the T4 templates in EF 4.0 were designed with this scenario in mind 🙂 There are 2 templates: One for the Entities themselves (i.e. ModelName.tt) One for the ObjectContext (i.e. ModelName.Context.tt) You should put the ModelName.tt file in you POCO project, and just change the template to point to the EDMX file in the … Read more