Difference between revisions of "Query"
From MidrangeWiki
m |
m |
||
| Line 1: | Line 1: | ||
[[Category:Programming]] | [[Category:Programming]] | ||
| + | [[Category:CaseTools]] | ||
Purists might say that Query/400 is not a "real" programming language, rather it is a CASE tool. I personally find that Query/400 is very powerful for rapid development of simple reports and inquiries, with many features that may be under-utilized. | Purists might say that Query/400 is not a "real" programming language, rather it is a CASE tool. I personally find that Query/400 is very powerful for rapid development of simple reports and inquiries, with many features that may be under-utilized. | ||
Revision as of 03:09, 26 May 2005
Purists might say that Query/400 is not a "real" programming language, rather it is a CASE tool. I personally find that Query/400 is very powerful for rapid development of simple reports and inquiries, with many features that may be under-utilized.
For example, I have a query that uses LIKE '%SOMETEXT%' to search fields of a data base for SOMETEXT where the % means I not care what stuff is in front of or behind the matching text.
I also have queries that create like *OUTFILEs that are then input to other queries.
Query/400 is a tool for accessing DB2/400 that is pretty safe to put into the hands of users, so long as we know how to prevent them from creating an *OUTFILE that gets same name as a pre-existing real file in our data base.
