AUA Framework training - Adding a new Entity named Student - Episode 6

Entity
Entity is the main concept, and indeed at the heart of the architecture of, the AUA framework. Each entity is defined by a class that contains its features and its relation to other entities. Each entity has an identifier that can be of any Data Type allowed in .NET, or it can be a combination of two or more Data Types allowed therein (combination key) .

Add Entities
Each entity inherits from the DomainEntity class, to which a primary key field called Id and one or more monitoring fields (depending on the setting type) are added .
It should be specified if the primary key has a data type other than the int data type (e.g. the Long data type is considered under the primary key)

By default the following fields are added to each entity. The Id key, the IsActive field and the RegistrationDate. The RegistrationDate displays the date and time the entity is created (automatically created inside SQL Server) and does not need to be filled in and sent .

The Id key of the primary key and its data type can be specified when defining an entity. The IsActive field shows whether the entity is active or inactive and it has a bool data type.

Entity Configs
There is a configuration class for each entity that can specify the length of field settings for it.

We configure the entity with the combination key as follows. The AppUserId and RoleId fields are both keys to the UserRole entity.

The entity without the identity key is configured as follows, in which case you send the initial value (ID) of the primary key to SQL Server.

The entity is configured without registering the deleted load (logical deletion).

Optional features
Identities without an identity key are configured as follows, in which case the main key is sent to the database.

Entity configuration, without considering deletion

Infrastructure .NetCore | asp.net core clean architecture | asp.net onion architecture | asp.net core mvc clean architecture | asp-net-core layered architecture | domain-driven design microservices example | domain driven design example c# asp.net | Asp.net Infrastructure Template C# | Clean Architecture Net Core Examplerefactor Inf | n-tier architecture net core 3.1 web api | asp.net core onion architecture | asp-net-core architecture best practices | clean architecture | clean architecture example | clean architecture design pattern | clean architecture onion asp.net | Domain-Driven Design in ASP.NET Core applications | Onion Architecture In ASP.NET Core With CQRS | Clean Architecture .Net Core | asp.net core architecture best practices | Designing a DDD-oriented microservice | net domain-driven design with c# source code | domain-driven design project structure | how to implement domain-driven design .net core | hands-on domain-driven design with .net core pdf | domain-driven design template | refactoring infrastructure net core | clean architecture net-core | entity on aua framework | entity on aua | entity relationship on aua framework | creating entity on aua framework | Adding Student Entity training in Asp.Net Unique Architecture | Adding a new Entity named Student in Asp.Net Unique Architecture | Asp.Net Unique Architecture AUA Framework training quite Free and professional

#entity - #addingentity

Full Document in this link👇👇:
https://auaframework.com/Document/Entity

If you think good architecture is expensive, try bad architecture.
I hope it will be useful for you, dear ones.
Just please don't forget to like, subscribe and comment if you like it.
Our social network address:
Website:
https://auaframework.com/
LinkedIn:
https://www.linkedin.com/company/aua-framework
GitHub:
https://github.com/AUAFramework/
YouTube:
https://www.youtube.com/channel/UCirDN-jMHpSGbhyik3jOKng

Видео AUA Framework training - Adding a new Entity named Student - Episode 6 канала Alfa