A while back I read Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin Series) which I thought had a ton of useful recommendarions....not all were entirely applicable to ObjectScript but still very useful.
https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture....
The Temp file often times uses a process private global
Process-private globals are written to the IRISTEMP database. In contrast to global variables, InterSystems IRIS does not treat a SET or KILL of a local variable or a process-private global as a journaled transaction event; rolling back the transaction has no effect on these operations.
That being said as Peter mentioned if you had an index on code_1_text you could greatly improve performance. In fact I suspect this type of query would be completely index satisfiable, ie the query would only examine the index and would not have to go to the mastermap for even better performance.
Depending on the legth of values for code_1_text if you do chose to add an index you might want to define the property as
Property code_!_text as %String(COLLATION="SQLUPPER(113)",MAXLEN=32000);
by setting the collation and length. If the values exceed the maximum global subscript length and you do not do this you could encounter <subscript> errors.
A subscript has an illegal value or a global reference is too long. For further details, refer to $ZERROR. For more information on maximum length of global references, see “Determining the Maximum Length of a Subscript”.
One important note about QuickStream. If you decide to go down this path you must make certain to Clear the QuickStream as part of your pipeline. The Message Purge that is set up as a task will purge the message header and the associated message body but when it looks at the message body all it sees is a property called QuickStreamId and it doesnt know it should also Clear the associated QuickStream object.