Michael Stephenson wrote:
On Wed, May 16, 2018 at 6:36 PM, Adrian Klaver
wrote:
On 05/16/2018 03:19 PM, hmidi slim wrote:
HI,
I'm working on a microservice application and I avoid using triggers
because they will not be easy to maintain and need an experimented
On Fri, May 18, 2018 at 12:45 PM, Melvin Davidson
wrote:
>
>
> > I have used triggers to keep audit-logs of changes to certain columns in
> a table
> Another good use for triggers is to maintain customer balance..EG: An
> INSERT, UPDATE or DELETE involving a customer
On Fri, May 18, 2018 at 9:35 AM, Vick Khera wrote:
> On Wed, May 16, 2018 at 6:19 PM, hmidi slim wrote:
>
>> HI,
>>
>> I'm working on a microservice application and I avoid using triggers
>> because they will not be easy to maintain and need an
hmidi slim writes:
> HI,
>
> I'm working on a microservice application and I avoid using triggers
> because they will not be easy to maintain and need an experimented person
> in database administration to manage them. So I prefer to manage the work
> in the application
On Wed, May 16, 2018 at 6:36 PM, Adrian Klaver
wrote:
> On 05/16/2018 03:19 PM, hmidi slim wrote:
>>
>> HI,
>>
>> I'm working on a microservice application and I avoid using triggers
>> because they will not be easy to maintain and need an experimented person in
>>
I've always found it most useful to consider the difference between "what
the system is" vs. "what the system does". The core data entities and their
stable relationships comprise most of what the system is. These are the
things that should be enforced at the lowest level possible (in a db
schema)
On 05/16/2018 03:19 PM, hmidi slim wrote:
HI,
I'm working on a microservice application and I avoid using triggers
because they will not be easy to maintain and need an experimented
person in database administration to manage them. So I prefer to manage
the work in the application using ORM