Обсуждение: infinite trigger loop
Hello, I would like to synchronize 2 tables. I think that maybe triggers are the best solution. But, if i create two update trigger, when i update the first table first trigger update the other, and the other trigger also try to update the first table... and this is an infinite loop. At now, in all two triggers i first drop the other and after the update recreate. I think that this is not the _best_ solution. Can you show me a better solution? thanks. PS: please CC: for my personal e-mail address, I'm not subscribed. Veres Lajos vlajos@ludens.elte.hu +36 20 438 5909
I don't know what you trigger are doing, but, you can't check if the update was already made? before try to update it!. On Mon, 12 May 2003, Veres Lajos wrote: > Hello, > > I would like to synchronize 2 tables. > I think that maybe triggers are the best solution. > But, if i create two update trigger, when i update the first table first > trigger update the other, and the other trigger also try to update the > first table... and this is an infinite loop. > At now, in all two triggers i first drop the other and after the update > recreate. > I think that this is not the _best_ solution. > Can you show me a better solution? > thanks. > > PS: > please CC: for my personal e-mail address, I'm not subscribed. > > Veres Lajos > vlajos@ludens.elte.hu > +36 20 438 5909 > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > -- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBD3AVWoRBACodcxl03gUoJOqgzRfAheGLKeri8MdDy8F3fX/LwIihpWQMwh6 goSEhp6f+VkINDJ3cX3OgTYVAIJLBrzzka2wbDHnTv9A7j8+VB4Nh2ZY9RrcZdxX g2z2NNdWVmxLPKTK+wbTXFsyLtj2IR0TASQdJKOL+VX6W7N/LYY2Mz4AXwCg8DC3 8cBi8P2ld48Un/Gvl1s/xHkD/j4r3WCsDGAzof2FiZ3wOkP9fgPbOk7v20FdXhOA hjmGY7GCb0tsEPALPj2St3BKVgTH7iJ08us9lIx9Kux9XV1ZhlkZr1G3A0bkgUfk Fcmih3FWmbV88Z4JFB1vhsrCFzgq3PHu5Wy37ObhpoVbs9ajo9vX09xZAL4SYq6o 7STAA/9UYgUwbB8fzG68Z7WLG8SDgEy5AL9ObHIUri+HeIHGSMtbjcksIMXkL1L5 CedPJDf/tphWrgvgROSWALJOvwc8cDAX/iwWyzAtmj+X8Xbx1QS0OJc8yPk4j9VI Fp7zusVbRprBaIuk3ur29WbDCGFUpkyBTIdxjyw04P+sjcIxObQtRXJpY2sgRGVu bmlzIChlRGVubmlzKSA8ZWRlbm5pc0Byb290c2hlbGwuYmU+iFcEExECABcFAj3A VWoFCwcKAwQDFQMCAxYCAQIXgAAKCRBAR/8wlx6vQEk5AJ0fK5oMOR7Xhh6ZU4qB Q4eFq6a/uQCcCgQ42duQ/0qgsmnu/aBcEi0EtHO5AQ0EPcBVbhAEAORKwkRPWpS5 qDe35p97UTcD2T2Oe2q29U2MV9Z5eDM5oPWYpXhGyIsKVUW2UyVpWfbVvLQfWVO+ ehfoDBHPI0GUZoOjjGBmwprII8hVc+YpJHnjTkB7ZoxNUlwCamuYXlNmQr6saQZO sfCJO9og64+25/OGZXmd2oOC/C1qeYmTAAMFA/4xRwY6r5m03lZI1hdlR/9PzC01 ZD46bTrhIYFAeZZmyVbsttmz3A0/gMxj2sxaHoFnQE4QO3xqAV8k2KvxNzArEuj/ rpu6SaFTBG+u7ikkkCb1hCgukF6kKIAZKP9QSsTGFVgBaUlaT6PLm7LMHq2Mauap OfztGsOfayzARNwu0IhGBBgRAgAGBQI9wFVuAAoJEEBH/zCXHq9A9FkAnjVE9wCa i1Gau6ypIxomane6UD3NAKDkl1ulR3iEsdy8fF99Oo95tSkawg== =86sd -----END PGP PUBLIC KEY BLOCK-----
Erick Dennis wrote: > I don't know what you trigger are doing, but, you can't check if the > update was already made? before try to update it!. Sort of a solution ... put "... AND att != OLD.att" into the updates performed by the triggers and it's not looping. Jan > > > On Mon, 12 May 2003, Veres Lajos wrote: > > >>Hello, >> >>I would like to synchronize 2 tables. >>I think that maybe triggers are the best solution. >>But, if i create two update trigger, when i update the first table first >>trigger update the other, and the other trigger also try to update the >>first table... and this is an infinite loop. >>At now, in all two triggers i first drop the other and after the update >>recreate. >>I think that this is not the _best_ solution. >>Can you show me a better solution? >>thanks. >> >>PS: >>please CC: for my personal e-mail address, I'm not subscribed. >> >>Veres Lajos >>vlajos@ludens.elte.hu >>+36 20 438 5909 >> >> >>---------------------------(end of broadcast)--------------------------- >>TIP 3: if posting/reading through Usenet, please send an appropriate >>subscribe-nomail command to majordomo@postgresql.org so that your >>message can get through to the mailing list cleanly >> > > -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #
On Fri, 16 May 2003, Erick Dennis wrote: > I don't know what you trigger are doing, but, you can't check if the > update was already made? before try to update it!. Yes finally, i choosed this method. a bit better. but the code is at least double size. Thanks for your response. > > > On Mon, 12 May 2003, Veres Lajos wrote: > > > Hello, > > > > I would like to synchronize 2 tables. > > I think that maybe triggers are the best solution. > > But, if i create two update trigger, when i update the first table first > > trigger update the other, and the other trigger also try to update the > > first table... and this is an infinite loop. > > At now, in all two triggers i first drop the other and after the update > > recreate. > > I think that this is not the _best_ solution. > > Can you show me a better solution? > > thanks. > > > > PS: > > please CC: for my personal e-mail address, I'm not subscribed. > > > > Veres Lajos > > vlajos@ludens.elte.hu > > +36 20 438 5909 > > > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 3: if posting/reading through Usenet, please send an appropriate > > subscribe-nomail command to majordomo@postgresql.org so that your > > message can get through to the mailing list cleanly > > > > -- > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > mQGiBD3AVWoRBACodcxl03gUoJOqgzRfAheGLKeri8MdDy8F3fX/LwIihpWQMwh6 > goSEhp6f+VkINDJ3cX3OgTYVAIJLBrzzka2wbDHnTv9A7j8+VB4Nh2ZY9RrcZdxX > g2z2NNdWVmxLPKTK+wbTXFsyLtj2IR0TASQdJKOL+VX6W7N/LYY2Mz4AXwCg8DC3 > 8cBi8P2ld48Un/Gvl1s/xHkD/j4r3WCsDGAzof2FiZ3wOkP9fgPbOk7v20FdXhOA > hjmGY7GCb0tsEPALPj2St3BKVgTH7iJ08us9lIx9Kux9XV1ZhlkZr1G3A0bkgUfk > Fcmih3FWmbV88Z4JFB1vhsrCFzgq3PHu5Wy37ObhpoVbs9ajo9vX09xZAL4SYq6o > 7STAA/9UYgUwbB8fzG68Z7WLG8SDgEy5AL9ObHIUri+HeIHGSMtbjcksIMXkL1L5 > CedPJDf/tphWrgvgROSWALJOvwc8cDAX/iwWyzAtmj+X8Xbx1QS0OJc8yPk4j9VI > Fp7zusVbRprBaIuk3ur29WbDCGFUpkyBTIdxjyw04P+sjcIxObQtRXJpY2sgRGVu > bmlzIChlRGVubmlzKSA8ZWRlbm5pc0Byb290c2hlbGwuYmU+iFcEExECABcFAj3A > VWoFCwcKAwQDFQMCAxYCAQIXgAAKCRBAR/8wlx6vQEk5AJ0fK5oMOR7Xhh6ZU4qB > Q4eFq6a/uQCcCgQ42duQ/0qgsmnu/aBcEi0EtHO5AQ0EPcBVbhAEAORKwkRPWpS5 > qDe35p97UTcD2T2Oe2q29U2MV9Z5eDM5oPWYpXhGyIsKVUW2UyVpWfbVvLQfWVO+ > ehfoDBHPI0GUZoOjjGBmwprII8hVc+YpJHnjTkB7ZoxNUlwCamuYXlNmQr6saQZO > sfCJO9og64+25/OGZXmd2oOC/C1qeYmTAAMFA/4xRwY6r5m03lZI1hdlR/9PzC01 > ZD46bTrhIYFAeZZmyVbsttmz3A0/gMxj2sxaHoFnQE4QO3xqAV8k2KvxNzArEuj/ > rpu6SaFTBG+u7ikkkCb1hCgukF6kKIAZKP9QSsTGFVgBaUlaT6PLm7LMHq2Mauap > OfztGsOfayzARNwu0IhGBBgRAgAGBQI9wFVuAAoJEEBH/zCXHq9A9FkAnjVE9wCa > i1Gau6ypIxomane6UD3NAKDkl1ulR3iEsdy8fF99Oo95tSkawg== > =86sd > -----END PGP PUBLIC KEY BLOCK----- > Veres Lajos lveres@vatera.com +36 20 438 5909