Yup, nothing unusual. it seems to be what is returned that whacks witango.
nope. this is an admin application. not accessible by visitors.
I've had some trouble crafting dynamic queries within a DirectDBMS due to the nosqlencoding configuration variable giving my either no quotes or two single quotes around my variable, when I just want one set of single quotes. (My workaround is to create the sql outside the DirectDBMS action). I mention this only because under some conditions, the sql that witango delivers is NOT the sql you wrote.
bill
On Dec 30, 2005, at 2:04 PM, Robert Garcia wrote:
dumb question, did you make sure that this taf was not bit by the !CST bug?
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
On Dec 30, 2005, at 1:51 PM, Roland Dumas wrote:
Have found that a crashing problem I have is the result of a query on a text field. Narrowed it down to a single field.
Is it possible for a text field to have some content that makes witango crash? I remember that the ¥ (yen) character was bad news when in a taf. Are there characters that will do harm when passed in a SELECT statement?
Roland A. Dumas
310 W. Bellevue Ave.
San Mateo, CA 94402
650-347-1373
415-412-9300 (cell)
AIM: radumas
Bill
William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
________________________________________________________________________
