| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 3871.1 |  | NOVA::SMITHI | Don't understate or underestimate Rdb! | Fri Mar 07 1997 12:54 | 23 | 
|  | Well SQL should tell you that the UPDATE is illegal.  You can not update a
cursor which contains a JOIN.  Please submit a BUG report.
Try this instead.
BEGIN 
	FOR :locrec 
		AS EACH ROW OF UPDATE ONLY TABLE CURSOR loc_phy_rows FOR 
			SELECT a.locator, b.dbkey
			FROM	locator_inventory AS a, 
				locator_physical AS b 
 
			WHERE	a.status = 35 AND 
				b.locator = a.locator AND 
				b.parcel_status IN (1,6,7,10,20,28) 
		DO 
			UPDATE locator_physical 
			SET	parcel_status = 2 
			WHERE	dbkey = :locrec.dbkey;
	END FOR; 
END; 
Ian
 | 
| 3871.2 |  | DUCATI::LASTOVICA | Is it possible to be totally partial? | Fri Mar 07 1997 12:54 | 1 | 
|  | note 3661.1 requested a BUG report.  Was one ever submitted?
 | 
| 3871.3 | thanks | M5::BLEHLBAC | RDB: 34% better than real life | Fri Mar 07 1997 13:36 | 7 | 
|  | 
re: .1
   ...  thanks Ian.
re: .2
   ...  I just KNEW someone would ask me that!!  I'll need to check.
 | 
| 3871.4 |  | DUCATI::LASTOVICA | Is it possible to be totally partial? | Fri Mar 07 1997 14:22 | 6 | 
|  | >re: .2
>   ...  I just KNEW someone would ask me that!!  I'll need to check.
	I was just guessing that since Ian had requested that you submit
one when you first reported the problem, one would have been submitted
then.
 | 
| 3871.5 | BugNo:464771 | M5::BLEHLBAC | RDB: 34% better than real life | Fri Mar 14 1997 08:08 | 9 | 
|  | 
>>	I was just guessing that since Ian had requested that you submit
>>one when you first reported the problem, one would have been submitted
>>then.
Well, I checked and it appears that I didn't.  I'll check to see if Jay did.
I apologize if we didn't.  I always try to accomodate the suggestions
and requests of the engineers to are kind enough to respond in the notes
conferences.  Anyway, I did bug this - BugNo:464771.
 | 
| 3871.6 | fixed in version 7.0 | NOVA::STONE |  | Mon Mar 24 1997 16:16 | 2 | 
|  | The bug was fixed in version 7.0.  Now a message will be returned explaining 
that the cursor is read only.
 |