Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2003
    Location
    The Netherlands
    Posts
    149

    Unanswered: multi user problem?

    Hello there,

    I'm avoiding a mutating table problem. A built a package(declared some arrays). I made a before-statement-trigger which deletes the arrays, a before-eachrow-trigger which fills the array with all the data and an after-statement trigger which does the actual processing. NOW!! What if someone updated a record and my after-statement trigger is busy with my array. Now, another user is updating another record from the same table. This will result in emptying the package which was used at that moment for processing of data. Is this possible and is there a workaround if it is possible?

  2. #2
    Join Date
    Sep 2002
    Location
    UK
    Posts
    5,171
    Provided Answers: 1

    Re: multi user problem?

    Originally posted by thepercival
    Hello there,

    I'm avoiding a mutating table problem. A built a package(declared some arrays). I made a before-statement-trigger which deletes the arrays, a before-eachrow-trigger which fills the array with all the data and an after-statement trigger which does the actual processing. NOW!! What if someone updated a record and my after-statement trigger is busy with my array. Now, another user is updating another record from the same table. This will result in emptying the package which was used at that moment for processing of data. Is this possible and is there a workaround if it is possible?
    Don't worry: package state (variables etc.) is private to each session, so there will be no conflict between users.

  3. #3
    Join Date
    Jan 2003
    Location
    The Netherlands
    Posts
    149

    sacasc

    thank you thousand times, we are very gracefull.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •