Subject | Re: [ib-support] lock conflict on no wait transaction - help please |
---|---|
Author | Svein Erling Tysvær |
Post date | 2002-06-04T07:53:41Z |
Hi again, John.
jbeh2000 wrote:
OK and ought to work. The fact that nobody else (not even Helen) has
replied to your question, indicates that there is no obvious error. Try the
following:
1) Drop your stored procedure.
2) Create it again using a few more ':' - i.e.
into :job_num, :job_id, :job_co, :date_opened, :DATE_COMMISSIONED,
:JOB_COMMISSIONED_STATUS, :WIP_PY_START, :WIP_CY_START, :wip_now
and
into :minsale, :maxsale
I suggest that you drop and create your procedure rather than use recreate
because of a former message on this list from Ded which solved a completely
different problem (shot in the dark), and the introduction of ':' simply
because I have no other ideas left. If this doesn't work, I'm out of ideas
and you have to either investigate further or shout loud enough for someone
else on this list to hear you.
Set
jbeh2000 wrote:
> As I understand it the update all occurs within the context of aWell, I'm no good with stored procedures, but to me your code looks pretty
> single transaction and I therefore don't understand what the lock
> conflict is.
OK and ought to work. The fact that nobody else (not even Helen) has
replied to your question, indicates that there is no obvious error. Try the
following:
1) Drop your stored procedure.
2) Create it again using a few more ':' - i.e.
into :job_num, :job_id, :job_co, :date_opened, :DATE_COMMISSIONED,
:JOB_COMMISSIONED_STATUS, :WIP_PY_START, :WIP_CY_START, :wip_now
and
into :minsale, :maxsale
I suggest that you drop and create your procedure rather than use recreate
because of a former message on this list from Ded which solved a completely
different problem (shot in the dark), and the introduction of ':' simply
because I have no other ideas left. If this doesn't work, I'm out of ideas
and you have to either investigate further or shout loud enough for someone
else on this list to hear you.
Set