Hi Juan,
I guess that my own case might be difficult if it is sever-dependent as you
indicate, becase I am going to develop my application with MS SQL sever
first and migrate it to DB2 later. Do you think it is feasible to go this
approach in practice with my case?
What do you mean by "caching of entity beans"? How does it relate to
the "trigger" event?
Thanks a lot.
-John
-----Original Message-----
From: Juan Lorandi (Chile) [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 3:41 PM
To: [EMAIL PROTECTED]
Subject: Re: "Trigger" method in EJB application
yes you can...
but different server implementations (specially, caching of entity beans)
might make this more difficult.
Be sure to desactivate cache's if appropiate for your server.
JP
> -----Original Message-----
> From: Jianguo Wang [mailto:[EMAIL PROTECTED]]
> Sent: Martes, 06 de Febrero de 2001 17:29
> To: [EMAIL PROTECTED]
> Subject: "Trigger" method in EJB application
>
>
> Dear friends,
>
> Can someone there give me a suggestion about the following question I
> am facing now?
>
> I have several tables, let's say tables A, B and C. It is
> required that,
> when A is updated, a portion of data from A will be populated
> into B and C.
> This process can be achieved through implementing A, B and C as entity
> beans.
>
> My question is if I can just use the "trigger" methods from
> database server
> to do the process of data populating without using beans at all.
>
> Thank you very much.
>
> -John
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
