Re: Witango-Talk: IS IN screws up

[Eric Weidl]

Hi,

Because the default array to text conversion is to an html table...

Normally the standard Search action is smart enough to convert an array to the proper comma-delimited syntax for an IS IN clause. I don't think a DirectDBMS is that helpful however. If it is a DirectDBMS action, convert the array to a comma delimited string, then use that variable in your SELECT statement.

I would also check the dimensions of the array. I don't think the automatic conversion works if the array is more than a single column.


Eric

----- Original Message -----
From: <mailto:[EMAIL PROTECTED]>James MacFarlane
To: <mailto:[EMAIL PROTECTED]>Multiple recipients of list witango-talk
Sent: Friday, December 06, 2002 1:58 PM
Subject: Witango-Talk: IS IN screws up

Every once in a while I go to use a query action that uses and IS IN clause like this:

SELECT M1.planVariantId FROM dbo.MassPriceLookup M1 WHERE (M1.priceGroupId=1 AND M1.VariantId in (11,11,2,2,3,3,30)

Get a syntax error, so I have the application dump out the SQL statement and it looks like this:

SELECT M1.planVariantId FROM dbo.MassPriceLookup M1 WHERE (M1.priceGroupId=1 AND M1.VariantId in (
11
11
2
2
3
3
30
)

So instead of dumping in comma-separated values, it puts in the HTML table of values. Why?!?!?!

I've included my screenshot of the query




________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body

________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
               with unsubscribe witango-talk in the message body