All:
Working with a projected temp table, to preserve live table data until a
solution is found.
Repeated attempts to UPDATE one column value, within 313 records,
consistently UPDATEs only the same ten (10) records.
This behaviour survives an UNLOAD/RELOAD operation, on an AUTOCHK'ed =
No Errors Found database.
Test Code: (Courier New)
--RB X.5E 10.5.2.20312
SET VAR vglcodenum TEXT = NULL
SET VAR vtaparentid INT = NULL
SET VAR vglcodenum = '56222'
SET VAR vtaparentid = 10346
UPDATE trxaction_tt +
SET glcodeid = t2.glcodeid +
FROM trxaction_tt t1, +
glcoa t2 +
WHERE t1.glcodeid = t2.glcodeid +
AND t2.glcodenum = .vglcodenum +
AND t1.taid IN +
( SELECT tasubid FROM tanesting +
WHERE taparentid = .vtaparentid )
RETURN
The Sub-Select clause produces the anticipated set of tasubid values,
each one being represented by multiple t1.taid instances in the
trxaction_tt table, totaling 313 records.
Hence the mystery. Thoughts?
Bruce A. Chitiea
SafeSectors, Inc.
112 Harvard Ave #272
Claremont CA 91711-4716
[email protected]
(909) 238-9012 c
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/em28323b6c-6a1f-42d5-970e-8973f87ae547%40pathfinder.
