OK...so I get that in Oracle you have Global Temp Tables whose structure is permanent, but whose data is temporary, so you can get something similar to what you have with SQL Server, except that you don't create the TT inside your SP instead you create it 'as part of the schema.'
Yet...somehow I don't like this....when I browse for my tables, I'm going to see hundreds of these temp tables cluttering up the list.
I can't help wondering if I'm missing the point.
Does the typical PL/SQL developer have a different approach to work tables? Tables which hold an intermediary result set which is required later in the script. I know I can use e.g. CTEs, but there scope is limited to a single statement, and while I do like CTEs in general, on occasions I've ripped them out and replaced them with temp tables for performance reasons.
So what does the Oracle dev do in these situations? The only other thing that springs to mind for persisting a recordset is a ..... cursor! I know that this isn't a dirty word in Oracle like it is in SQL - but I still don't understand fully why not.
I'm finding the learning curve from SQL to Oracle steeper than I imagined....and that bit of the curve where I currently find myself really sucks.
Thanks for any input!