search

patrickTingen / DataDigger

A dynamic dataviewer for your Progress / OpenEdge databases
https://datadigger.wordpress.com/
MIT License
50 stars 23 forks source link

Error when try to update/delete record with trigger #51

Closed dlabas2 closed 4 years ago

dlabas2 commented 4 years ago

When I start DataDigger and try to update a record that has a trigger, the following error occurs:

image

After restarting DataDigger in the same session everything works fine.

Thank you very much!!!

patrickTingen commented 4 years ago

Hi, thanks for using DataDigger and reporting this issue.

In this case, DataDigger does not have the path to your triggers and cannot execute them. If you want to change the record without the trigger, you can uncheck the box at the bottom of the screen:

[image: image.png] Then DataDigger will skip the trigger. If you insist on the trigger to fire when you update a record, then make sure the trigger is in the propath of the session where you run DataDigger.

Kind regards, Patrick Tingen

Op do 5 dec. 2019 om 12:35 schreef dlabas2 notifications@github.com:

When I start DataDigger and try to update a record that has a trigger, the following error occurs:

[image: image] https://user-images.githubusercontent.com/42679532/70231918-90619b00-175b-11ea-918e-7b63e51bbe0d.png

After restarting DataDigger in the same session everything works fine.

Thank you very much!!!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHKRELBXVHZLGGTURB3QXDRRRA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6JOQUQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABN3AHNM66FJNAFGNDHDAD3QXDRRRANCNFSM4JVYGU3Q .

dlabas2 commented 4 years ago

Thank you for your reply.

But in version 24 (20181114) everything works fine. And if in the same session restart DataDiger everything works fine (no PROPATH change). The error indicates that the database is incorrect.

[cid:fd3db936-25cd-45bf-8b4f-972cbb7a8e69]

:-) Sretno! Good Luck! Nemojte se bojati! :-)

Dubravko Labašhttp://aka.ms/weboutlook mob. +385 98 9827841

From: Patrick Tingen notifications@github.com Sent: Thursday, December 5, 2019 12:40 To: patrickTingen/DataDigger DataDigger@noreply.github.com Cc: dlabas2 dubravko.labas@vz.t-com.hr; Author author@noreply.github.com Subject: Re: [patrickTingen/DataDigger] Error when try to update/delete record with trigger (#51)

Hi, thanks for using DataDigger and reporting this issue.

In this case, DataDigger does not have the path to your triggers and cannot execute them. If you want to change the record without the trigger, you can uncheck the box at the bottom of the screen:

[image: image.png] Then DataDigger will skip the trigger. If you insist on the trigger to fire when you update a record, then make sure the trigger is in the propath of the session where you run DataDigger.

Kind regards, Patrick Tingen

Op do 5 dec. 2019 om 12:35 schreef dlabas2 notifications@github.com:

When I start DataDigger and try to update a record that has a trigger, the following error occurs:

[image: image] https://user-images.githubusercontent.com/42679532/70231918-90619b00-175b-11ea-918e-7b63e51bbe0d.png

After restarting DataDigger in the same session everything works fine.

Thank you very much!!!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHKRELBXVHZLGGTURB3QXDRRRA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6JOQUQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABN3AHNM66FJNAFGNDHDAD3QXDRRRANCNFSM4JVYGU3Q .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=AKFTZ3COQXBXBN2HHZQIIZLQXDSDPA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGAN5GA#issuecomment-562093720, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKFTZ3C6IDP4PEPCINY7U2TQXDSDPANCNFSM4JVYGU3Q.

patrickTingen commented 4 years ago

Then I should probably look into this a bit more. Can you give some more information on your case?

Kind regards Patrick Tingen

Op do 5 dec. 2019 om 13:11 schreef dlabas2 notifications@github.com:

Thank you for your reply.

But in version 24 (20181114) everything works fine. And if in the same session restart DataDiger everything works fine (no PROPATH change). The error indicates that the database is incorrect.

[cid:fd3db936-25cd-45bf-8b4f-972cbb7a8e69]

:-) Sretno! Good Luck! Nemojte se bojati! :-)

Dubravko Labašhttp://aka.ms/weboutlook mob. +385 98 9827841

From: Patrick Tingen notifications@github.com Sent: Thursday, December 5, 2019 12:40 To: patrickTingen/DataDigger DataDigger@noreply.github.com Cc: dlabas2 dubravko.labas@vz.t-com.hr; Author < author@noreply.github.com> Subject: Re: [patrickTingen/DataDigger] Error when try to update/delete record with trigger (#51)

Hi, thanks for using DataDigger and reporting this issue.

In this case, DataDigger does not have the path to your triggers and cannot execute them. If you want to change the record without the trigger, you can uncheck the box at the bottom of the screen:

[image: image.png] Then DataDigger will skip the trigger. If you insist on the trigger to fire when you update a record, then make sure the trigger is in the propath of the session where you run DataDigger.

Kind regards, Patrick Tingen

Op do 5 dec. 2019 om 12:35 schreef dlabas2 notifications@github.com:

When I start DataDigger and try to update a record that has a trigger, the following error occurs:

[image: image] < https://user-images.githubusercontent.com/42679532/70231918-90619b00-175b-11ea-918e-7b63e51bbe0d.png

After restarting DataDigger in the same session everything works fine.

Thank you very much!!!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHKRELBXVHZLGGTURB3QXDRRRA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6JOQUQ , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABN3AHNM66FJNAFGNDHDAD3QXDRRRANCNFSM4JVYGU3Q

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=AKFTZ3COQXBXBN2HHZQIIZLQXDSDPA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGAN5GA#issuecomment-562093720>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AKFTZ3C6IDP4PEPCINY7U2TQXDSDPANCNFSM4JVYGU3Q

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHOADHR2PHYGWUOGEBDQXDVYRA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGAQJAY#issuecomment-562103427, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABN3AHK5HOIDJXTSL53BL5DQXDVYRANCNFSM4JVYGU3Q .

dlabas2 commented 4 years ago

Hi,

:-) Sretno! Good Luck! Nemojte se bojati! :-)

Dubravko Labašhttp://aka.ms/weboutlook mob. +385 98 9827841

From: Patrick Tingen notifications@github.com Sent: Thursday, December 5, 2019 13:18 To: patrickTingen/DataDigger DataDigger@noreply.github.com Cc: dlabas2 dubravko.labas@vz.t-com.hr; Author author@noreply.github.com Subject: Re: [patrickTingen/DataDigger] Error when try to update/delete record with trigger (#51)

Then I should probably look into this a bit more. Can you give some more information on your case?

Kind regards Patrick Tingen

Op do 5 dec. 2019 om 13:11 schreef dlabas2 notifications@github.com:

Thank you for your reply.

But in version 24 (20181114) everything works fine. And if in the same session restart DataDiger everything works fine (no PROPATH change). The error indicates that the database is incorrect.

[cid:fd3db936-25cd-45bf-8b4f-972cbb7a8e69]

:-) Sretno! Good Luck! Nemojte se bojati! :-)

Dubravko Labašhttp://aka.ms/weboutlook mob. +385 98 9827841

From: Patrick Tingen notifications@github.com Sent: Thursday, December 5, 2019 12:40 To: patrickTingen/DataDigger DataDigger@noreply.github.com Cc: dlabas2 dubravko.labas@vz.t-com.hr; Author < author@noreply.github.com> Subject: Re: [patrickTingen/DataDigger] Error when try to update/delete record with trigger (#51)

Hi, thanks for using DataDigger and reporting this issue.

In this case, DataDigger does not have the path to your triggers and cannot execute them. If you want to change the record without the trigger, you can uncheck the box at the bottom of the screen:

[image: image.png] Then DataDigger will skip the trigger. If you insist on the trigger to fire when you update a record, then make sure the trigger is in the propath of the session where you run DataDigger.

Kind regards, Patrick Tingen

Op do 5 dec. 2019 om 12:35 schreef dlabas2 notifications@github.com:

When I start DataDigger and try to update a record that has a trigger, the following error occurs:

[image: image] < https://user-images.githubusercontent.com/42679532/70231918-90619b00-175b-11ea-918e-7b63e51bbe0d.png

After restarting DataDigger in the same session everything works fine.

Thank you very much!!!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHKRELBXVHZLGGTURB3QXDRRRA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6JOQUQ , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABN3AHNM66FJNAFGNDHDAD3QXDRRRANCNFSM4JVYGU3Q

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=AKFTZ3COQXBXBN2HHZQIIZLQXDSDPA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGAN5GA#issuecomment-562093720>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AKFTZ3C6IDP4PEPCINY7U2TQXDSDPANCNFSM4JVYGU3Q

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHOADHR2PHYGWUOGEBDQXDVYRA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGAQJAY#issuecomment-562103427, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABN3AHK5HOIDJXTSL53BL5DQXDVYRANCNFSM4JVYGU3Q .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=AKFTZ3AVD6ZWQCL5CFNJZHLQXDWQRA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGAQYUY#issuecomment-562105427, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKFTZ3BH7RUKQVST7HGTIHLQXDWQRANCNFSM4JVYGU3Q.

patrickTingen commented 4 years ago

Hi Dubravko,

I am looking into this, but I cannot reproduce it. I tried it with a database with write trigger, with delete trigger, defined inside db and as separate .p, but everytime the trigger fires. Since you only experience this the first time you try it, could it be that there is something else in your session doing something with the dictdb alias? I investigated all parts of DD that do something with dictdb, but the truth is, it are not that many and I cannot find anything wrong with it.

Would it be possible for you to try to reproduce it in a separate session against the sports db?

Patrick Tingen

Op do 5 dec. 2019 om 15:23 schreef dlabas2 notifications@github.com:

Hi,

:-) Sretno! Good Luck! Nemojte se bojati! :-)

Dubravko Labašhttp://aka.ms/weboutlook mob. +385 98 9827841

From: Patrick Tingen notifications@github.com Sent: Thursday, December 5, 2019 13:18 To: patrickTingen/DataDigger DataDigger@noreply.github.com Cc: dlabas2 dubravko.labas@vz.t-com.hr; Author < author@noreply.github.com> Subject: Re: [patrickTingen/DataDigger] Error when try to update/delete record with trigger (#51)

Then I should probably look into this a bit more. Can you give some more information on your case?

  • Is your trigger in the propath? YES
  • Do you use customizations via myDataDigger.p? NO
  • Is there a delete validation on the record? NO
  • Do you use DICTDB inside the trigger? NO

Kind regards Patrick Tingen

Op do 5 dec. 2019 om 13:11 schreef dlabas2 notifications@github.com:

Thank you for your reply.

But in version 24 (20181114) everything works fine. And if in the same session restart DataDiger everything works fine (no PROPATH change). The error indicates that the database is incorrect.

[cid:fd3db936-25cd-45bf-8b4f-972cbb7a8e69]

:-) Sretno! Good Luck! Nemojte se bojati! :-)

Dubravko Labašhttp://aka.ms/weboutlook mob. +385 98 9827841

From: Patrick Tingen notifications@github.com Sent: Thursday, December 5, 2019 12:40 To: patrickTingen/DataDigger DataDigger@noreply.github.com Cc: dlabas2 dubravko.labas@vz.t-com.hr; Author < author@noreply.github.com> Subject: Re: [patrickTingen/DataDigger] Error when try to update/delete record with trigger (#51)

Hi, thanks for using DataDigger and reporting this issue.

In this case, DataDigger does not have the path to your triggers and cannot execute them. If you want to change the record without the trigger, you can uncheck the box at the bottom of the screen:

[image: image.png] Then DataDigger will skip the trigger. If you insist on the trigger to fire when you update a record, then make sure the trigger is in the propath of the session where you run DataDigger.

Kind regards, Patrick Tingen

Op do 5 dec. 2019 om 12:35 schreef dlabas2 notifications@github.com:

When I start DataDigger and try to update a record that has a trigger, the following error occurs:

[image: image] <

https://user-images.githubusercontent.com/42679532/70231918-90619b00-175b-11ea-918e-7b63e51bbe0d.png

After restarting DataDigger in the same session everything works fine.

Thank you very much!!!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <

https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHKRELBXVHZLGGTURB3QXDRRRA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H6JOQUQ

, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ABN3AHNM66FJNAFGNDHDAD3QXDRRRANCNFSM4JVYGU3Q

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<

https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=AKFTZ3COQXBXBN2HHZQIIZLQXDSDPA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGAN5GA#issuecomment-562093720 , or unsubscribe<

https://github.com/notifications/unsubscribe-auth/AKFTZ3C6IDP4PEPCINY7U2TQXDSDPANCNFSM4JVYGU3Q

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHOADHR2PHYGWUOGEBDQXDVYRA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGAQJAY#issuecomment-562103427 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABN3AHK5HOIDJXTSL53BL5DQXDVYRANCNFSM4JVYGU3Q

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub< https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=AKFTZ3AVD6ZWQCL5CFNJZHLQXDWQRA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGAQYUY#issuecomment-562105427>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AKFTZ3BH7RUKQVST7HGTIHLQXDWQRANCNFSM4JVYGU3Q

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHKSUEGSDHIO5HE3CQ3QXEFHNA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGA3YFY#issuecomment-562150423, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABN3AHL3TS35DJ7VJTV6TRLQXEFHNANCNFSM4JVYGU3Q .

dlabas2 commented 4 years ago

Triggers on base use dictdb alias when logging changes. When does DataDigger first start, this alias dictdb is set to? and then errors occur. When I close DataDigger and restart the alias dictdb is set on the first active database. The document encloses a modified DataDigger.p program and messages that appear when the program starts. Thank you very much!!!

DataDigger_DictDb.docx

patrickTingen commented 4 years ago

Thanks for the document. If I look at it, at the point of message 3 it shows that cDictDb = ?. This surprises me a bit, but I can reproduce it here. In the starting program, datadigger.p, this is solved by setting back the dictdb alias to the same as what it was before DD started, but wile DD is active, the alias is also not set. I made a change to always set dictdb to the currently selected database. If you get the latest version from Github (dev branch), you will have this change. Can you check if this will work for you?

Patrick Tingen

Op wo 8 jan. 2020 om 08:35 schreef dlabas2 notifications@github.com:

Triggers on base use dictdb alias when logging changes. When does DataDigger first start, this alias dictdb is set to? and then errors occur. When I close DataDigger and restart the alias dictdb is set on the first active database. The document encloses a modified DataDigger.p program and messages that appear when the program starts. Thank you very much!!!

DataDigger_DictDb.docx https://github.com/patrickTingen/DataDigger/files/4034047/DataDigger_DictDb.docx

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHLJKH4T7MPX5ECTGF3Q4V65VA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEILOWII#issuecomment-571927329, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABN3AHPQPRZRZI6KSBXAUI3Q4V65VANCNFSM4JVYGU3Q .

dlabas2 commented 4 years ago

I checked and everything works fine. Thank you very much!!!

patrickTingen commented 4 years ago

You're welcome, and thank /you/ for reporting this.

Cheers! Patrick Tingen

Op vr 10 jan. 2020 om 09:15 schreef dlabas2 notifications@github.com:

I checked and everything works fine. Thank you very much!!!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/patrickTingen/DataDigger/issues/51?email_source=notifications&email_token=ABN3AHILLGD7QKQ776UEXO3Q5AVCTA5CNFSM4JVYGU32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEITBZCI#issuecomment-572923017, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABN3AHMSMXIG4ST4NXWHJX3Q5AVCTANCNFSM4JVYGU3Q .