Click to download the source file Yet another article about MONGO! This article is about retrieving data in mongo and tweaking the retrieval method to accommodate some project requirements. I am not an expert in working with Expression trees, but some methods are quite easy to use and provide a great deal of flexibility inRead more
With mongo some operations will return a dynamic object, usually wrapped in an expando object. To deserialize the expando object in the target class is quite simple, I actually looked in the source code to see how the driver performs this operation. If you look at the test involving the dynamic type here (https://github.com/mongodb/mongo-csharp-driver/blob/b473de06f9bf3587b3a00f52ba2678d9aed71d74/tests/MongoDB.Bson.Tests/Serialization/Serializers/ObjectSerializerTests.cs) youRead more
The mongo driver offers a rich and complete infrastructure to create rich domain entities out of the box. The bson serializer integrated with the mongo driver can tackle all types of entities, it can deserialize entities with private setters and constructors, allowing us to define our entity methods and limit property access. Cloning an entityRead more
With mongo you can enrich you queries with projection definitions, making it easy to limit the data you retrieve from the database and also shape the data according to your projects preferences. I will show several ways to achieve projections and some limitations regarding these. In our example we will use the base class Person,Read more
A NoSql database provides a different way of storing and handling data then the classical sql. While in a relational environment you have to split your models into logical components and store them in different tables using relations to define how will they be grouped together, in NoSql you work with json-like formats and thisRead more
In the previous article I’ve talked about the use of a Value Object and you’ve seen the advantages of a value object in practice. One challenge that occurs is regarding saving value objects in a database. And you will see why. Let’s define our entity class:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 |
public class Email : ValueObject<string> { public Email() { //for expando deserializer } public Email(SerializationInfo info, StreamingContext context) { //The special constructor is used to deserialize values. this.GetObjectData(info, context); } public static Email Create(string value) { return new Email { Value = value }; } public override int CompareTo(ValueObject<string> other) { return this.Value.CompareTo(other.Value); } protected override bool EqualsCore(object obj) { if (obj is null) return false; if (obj is ValueObject<string> vo) { return this.Value == vo.Value; } return false; } protected override int GetHashCodeCore() { return this.Value.GetHashCode(); } protected override void Validators(ValidationBuilder<string, string> validators) { validators.Add(x => (!string.IsNullOrEmpty(x)) ? ValidationResult<string>.Success() : ValidationResult<string>.Fail("Email cannot be empty"), 0); } } |
|
1 2 3 4 5 |
public class ContactDetails : BasicEntity { [BsonElement("Email")] public Email Email { get; set; } } |
This model contains an email value object.Read more
