Ahhh, but see, my memory is fuzzy. I was only thinking about the top half of your question. The bottom half had already slipped from my mind when I started typing my reply.
Man I must be getting old :-P Scott, On Monday, March 17, 2008 3:56pm, "Wolf, Gene" <[EMAIL PROTECTED]> said: > Your memory is not that fuzzy. *laughs* What you pointed out is the same > code you get if you open a SQL window and drag a query action into it. > However, I want to write the actual query string to a database and that > little trick does not help. For example, if a query action have three > vars in the criteria section and two of them are null the string > generated completely omits those conditions. Rightly so. So I would like > to be able to see what the SQL generated code is on every execution of a > given query action and I'll be damned if I can find a way of doing it in > Witango. > > If Robert has requested this feature I suspect there is no way to > currently do this in Witango. > > -----Original Message----- > From: Scott Cadillac [mailto:[EMAIL PROTECTED] > Sent: Monday, March 17, 2008 2:47 PM > To: [email protected] > Subject: RE: Witango-Talk: SQL Generated Query > > Hi Gene, > > If my fuzzy memory serves me correctly, if you right-click on a database > Action, you should have an option for "SQL Query", which opens a little > query utility that contains your generated SQL statement. I think it may > also contain your metatags (for your WHERE clause arguments and such) > but not the actual values. > > Hope that helps. > > Scott, > > > > On Monday, March 17, 2008 3:24pm, Robert Shubert <[EMAIL PROTECTED]> > said: > >> <@SQL> is populated with the last run SQL statement - except for the >> fact that bound values are not shown, which means that you may need to > >> do additional work in certain places to know what was in the bindings. > >> This is my #1 request for v6. >> >> >> >> Robert >> >> >> >> _____ >> >> From: Wolf, Gene [mailto:[EMAIL PROTECTED] >> Sent: Monday, March 17, 2008 2:17 PM >> To: [email protected] >> Subject: Witango-Talk: SQL Generated Query >> >> >> >> Easy question. Is there any way of obtaining, from Witango, the >> actual SQL code generated by searches? I know the code is available in > >> the debug dump but It would be really handy to be able to pull a >> variable that contains that code and be able to write it to a database > >> file for testing and checking. I'd really like to be able to write >> this code to a database table where I could record employee ID, date > and time requested, etc. >> >> Thoughts on how to accomplish this? >> >> Gene Wolf >> Supervisor, Business Systems >> DRS Sensors & Targeting Systems-Optronics 2330 Commerce Park Drive NE >> Palm Bay, Florida 32905 >> Phone: 321-309-0685 >> 321-309-0202 (fax) >> >> Dictionary.com Word of the Day >> <http://dictionary.reference.com/wordoftheday/> >> http://dictionary.reference.com/wordoftheday/ >> >> This e-mail, including any attached files, may contain confidential >> and privileged information for the sole use of the intended recipient. > >> Any review, use, distribution, or disclosure by others is strictly > prohibited. >> If you are not the intended recipient (or authorized to receive >> information for the intended recipient), please contact the sender by >> reply e-mail and delete all copies of this message. >> >> "This (document/presentation) may contain technical data as defined in > >> the International Traffic In Arms Regulations (ITAR) 22 CFR 120.10. >> Export of this material is restricted by the Arms Export Control Act >> (22 U.S.C. 2751 et seq.) and may not be exported to foreign persons >> without prior written approval from the U.S. Department of State." >> >> >> >> ______________________________________________________________________ >> __ >> >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> >> ______________________________________________________________________ >> __ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
