Select * from orders LEFT OUTER JOIN gift_cards on orders.order_number = gift_cards.order_number WHERE orders.order_number = <@ARG orders_uid1>
Looking at your query, you are only requesting cols from orders table, and the criteria is only from orders table. So why the join? Am I missing something?
I was going to suggest ANSI syntax, and show you what I meant, then I realized this query only needs one table.
select * from orders where order_number = <@arg orders_uid1>
And assuming order_number is an unquoted datatype like an int.
--
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 Nov 19, 2005, at 8:11 PM, Roland Dumas wrote:
On Nov 19, 2005, at 6:56 PM, Robert Shubert wrote:
Oh, and are you using either of the special Witango features like "Get total row count", "number of rows to retrieve" or "start retrieval at" ??
here's how simple it is: Select * from orders LEFT OUTER JOIN gift_cards on orders.order_number = gift_cards.order_number WHERE orders.order_number = <@ARG orders_uid1>
I'd think if it were bad, it would always be bad.
-----Original Message----- Sent: Saturday, November 19, 2005 9:36 PM Subject: Re: Witango-Talk: crashing witango 5 on OS X
sure. and WITH witango it works usually. Interesting thing is that when it crashes, it does so only on the first hit of a record. You can pound on the record to see if it will crash again, and it won't. The records that are associated with crashes are not out of the ordinary at all and have nothing in common. The crashed thread is always the same - exactly the same.
On Nov 19, 2005, at 3:20 PM, William M Conlon wrote:
Can you execute the problematic query directly against your db, without witango?
On Nov 19, 2005, at 2:41 PM, Roland Dumas wrote:
and it crashes witango still...... this is befuddling....
On Nov 19, 2005, at 11:35 AM, Roland Dumas wrote:
I've changed from witango generated sql to a direct dbms. Also changed column from tinytext to varchar. I'll know if that resolved the issue the next time a batch of orders is processed. Thanks for all the ideas, folks.
On Nov 18, 2005, at 11:18 AM, Robert Shubert wrote:
I would definitely try a directdbms in that case, get away from the SQL generator. The NULL could be an issue. Personally I'm in the habit of making flags that contain a 0 or a 1 and block the NULL case. It's entirely possible that there's some glitch in dealing with the NULL column.
On other thing would be to trace the DB. You'd like to know if the SQL statement is getting to the SQL server or not.
Robert
________________________________________________________________________
________________________________________________________________________
Roland A. Dumas 310 W. Bellevue Ave. San Mateo, CA 94402 650-347-1373 415-412-9300 (cell) AIM: radumas
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
|
