Thanks for answer. I am in sync with your answer.
I believe their is no risk from SQLite3 point of view to handle the mentioned case. On Fri, Nov 1, 2013 at 6:47 PM, Igor Tandetnik <[email protected]> wrote: > On 11/1/2013 5:58 AM, techi eth wrote: > >> 1) Is process – B will allow to Insert? >> > > Sure, why not. > > > 2) If allowed then it will select notify function from process – B or >> Process - A? >> > > The custom function will be called in process B - the process doing the > insertion. > > > 3) If all works then what risk I will carry? (Like deleting row, >> deleting trigger will crate any issue?) >> > > I'm not sure I understand the question. Deleting a row will delete a row. > Deleting a trigger will delete a trigger. Whether those are "issues" in > your design is for you to decide. > > > I assume answer will valid for other operation like update & delete >> operation as well. >> > > Yes, nothing changes if you replace AFTER INSERT with AFTER UPDATE or > AFTER DELETE. > -- > Igor Tandetnik > > ______________________________**_________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-**bin/mailman/listinfo/sqlite-**users<http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users> > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
