At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
At what point does data accessmanipulation logic becomes business logic?
Consider a service which updates PersonDetail tables in database. I am Using EF which maps the table to this Entity. When a record is updated, it is not actually updated but a new record is created and old one is made history by setting HistoryCode to 0
Should We Use Surrogate Primary Keys for Every Table? [duplicate]
Technology stack (no way to dynamically map these import files in
SSIS, need lot of dynamic SQL or java/c#)
Removing dependencies on subclass-specific behavior
I have a Message class which can contain multiple types of payloads (or sometimes no payload), each derived from a common Payload class. However, this becomes problematic because the Message class wants to know about the Payload subclasses for various reasons such as:
Injecting dependencies (DI) in c++ applications
I am playing with dependency injection, but i am not sure I am doing it right.
Especially, I am not sure what should be the correct way to build classes with injected dependencies.
Injecting dependencies (DI) in c++ applications
I am playing with dependency injection, but i am not sure I am doing it right.
Especially, I am not sure what should be the correct way to build classes with injected dependencies.
Injecting dependencies (DI) in c++ applications
I am playing with dependency injection, but i am not sure I am doing it right.
Especially, I am not sure what should be the correct way to build classes with injected dependencies.
Injecting dependencies (DI) in c++ applications
I am playing with dependency injection, but i am not sure I am doing it right.
Especially, I am not sure what should be the correct way to build classes with injected dependencies.