You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: mORMot 1 » DDD and many-to-many or one-to-many relationships » 2015-10-13 13:10:24
I want to see how my business logic displayed in the database. This will be one, two or three table in Database?
#2 Re: mORMot 1 » DDD and many-to-many or one-to-many relationships » 2015-10-13 09:01:39
But in this case in database created one table with more records? Then if in our each Company and Emploee contains 1000 or more record?
#3 Re: mORMot 1 » ID field in the DTO - Mormot DDD » 2015-10-13 04:48:54
Most of the time, you could use a real-world identifier for the aggregate.
Like a serial number, a client code, a logon name, an account number, an invoice reference or an ISBN.
I fully agree, but sometimes there is a need to get our "computer specific" ID. But still we try to follow these recommendations.
I take this opportunity to thank you for a wonderful framework.
#4 Re: mORMot 1 » ID field in the DTO - Mormot DDD » 2015-10-12 12:29:12
The ID is to be retrieved outside the aggregate properties, e.g. via the TDDDRepositoryRestQuery.CurrentORMInstance property.
Then you can create your DTO gathering both the TSynPeristent aggregate and CurrentORMInstance.ID.
can be more about it?
Pages: 1