join without use of UNION 2

[Guest_imported]

Table A contains a reference no, a date, & an amount, for transactions up to & including yesterday. Table B contains the same 3 fields for today's transactions. Reference Numbers in Table A might not be in Table B. I need to write a VIEW to merge them, for later use in a Stored Procedure.
I cannot, however use a "UNION" in my VIEW to achieve this, as my run-time environment returns an error.

 

[MalcolmW]

Why not merge your two "tables" in your stored procedure, and avoid this problem altogether? Malcolm

 

[ianholmes]

Thanks Malcolm, but Table A is absolutely ginormous, & so this obvious option isn't a starter.

 

[carp]

Your view may be failing because UNION requires a sort, which tends to fail within a view specification. However, UNION ALL does not do a sort since it does not try to weed out duplicate rows. This might just do the trick for you.

 

[carp]

I just tried creating a view with a UNION in Oracle and it works OK. What RDBMS are you using?

 

[ianholmes]

Thanks Carp.
I get the message "Set Operators May Not Appear Within The Definition Of A View" when I use "Union" or "Union All" in my VIEW, hence the need to program around this limitation.
The o/s is AIX 4.1.4, with a SYBASE 11.5.1 DB.
Help !

 

[THoey]

I don't know Sybase, but some how, I get the feeling there is something else causing this error. Any chance you can paste the code here? Terry M. Hoey
th3856@txmail.sbc.com
While I don't mind e-mail messages, please post all questions in these forums for the benefit of all members.

 

[karluk]

Sadly, this is a real limitation of Sybase. I found a number of hits on this error at Sybase's web site. The following link suggests a possible work-around.

http://webforums.sybase.com/nntp/nd000056.nsf/docid/0f5b2df7171f1f1f14142538fb986990