tag:blogger.com,1999:blog-18037024.post112988679961067390..comments2024-02-16T14:33:11.277+01:00Comments on Annals of Oracle's Improbable Errors: ORA-00904 and MERGEByte64http://www.blogger.com/profile/15629209362377395020noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-18037024.post-79499236509649355042007-11-06T16:30:00.000+01:002007-11-06T16:30:00.000+01:00You get the same error using MERGE if you try to u...You get the same error using MERGE if you try to update the joined columns. (See http://forums.oracle.com/forums/thread.jspa?threadID=341012.) C'mon Oracle, is it that hard to create a new error number for this?Unknownhttps://www.blogger.com/profile/00638201295950178542noreply@blogger.comtag:blogger.com,1999:blog-18037024.post-10414503583824475192007-03-07T17:20:00.000+01:002007-03-07T17:20:00.000+01:00Excellent ! Thanks for this last comment: the ora...Excellent !<BR/><BR/> Thanks for this last comment: the oracle doc doesn't talk about this (logical) limitation.<BR/><BR/>EtienneAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-18037024.post-1166002089747535662006-12-13T10:28:00.000+01:002006-12-13T10:28:00.000+01:00Moreover, the error 00904 came about not because o...Moreover, the error 00904 came about not because of a missing comma, but because the condition in the ON clause contains a reference to a column in the UPDATE statement (when matched).<BR/>This is apparently an undocumented "feature".<BR/>By leaving out the b column in the update statement, you made the statement work.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-18037024.post-1156858453983474012006-08-29T15:34:00.000+02:002006-08-29T15:34:00.000+02:00Excellent explanation, thank you!Excellent explanation, thank you!Byte64https://www.blogger.com/profile/15629209362377395020noreply@blogger.comtag:blogger.com,1999:blog-18037024.post-1156856467765840782006-08-29T15:01:00.000+02:002006-08-29T15:01:00.000+02:00It probably interpreted "c" as a column alias for ...It probably interpreted "c" as a column alias for "b", so the only columns available to the t2 "table" were "a", "c", & "d"Anonymousnoreply@blogger.com