Scott Haneda wrote:
on 10/28/05 5:52 AM, Brent Baisley at [EMAIL PROTECTED] wrote:
You can nest the IF statement, putting another where 'soon' is like
Jasper suggested. Or you can use the CASE WHEN THEN construct if you
have a lot of conditions you need to check for.
Can you show me an examp
on 10/28/05 5:52 AM, Brent Baisley at [EMAIL PROTECTED] wrote:
> You can nest the IF statement, putting another where 'soon' is like
> Jasper suggested. Or you can use the CASE WHEN THEN construct if you
> have a lot of conditions you need to check for.
Can you show me an example of the CASE meth
You can nest the IF statement, putting another where 'soon' is like
Jasper suggested. Or you can use the CASE WHEN THEN construct if you
have a lot of conditions you need to check for.
On Oct 28, 2005, at 12:22 AM, Scott Haneda wrote:
on 10/27/05 6:34 PM, Scott Haneda at [EMAIL PROTECTED]
On Thu, 2005-10-27 at 21:22 -0700, Scott Haneda wrote:
> on 10/27/05 6:34 PM, Scott Haneda at [EMAIL PROTECTED] wrote:
>
> > Right now, my update works as follows, and works fine, however, I want to do
> > a condition to say if products.ship_status = 1 then set
> > cart_test.shipping_status to 'no
on 10/27/05 6:34 PM, Scott Haneda at [EMAIL PROTECTED] wrote:
> Right now, my update works as follows, and works fine, however, I want to do
> a condition to say if products.ship_status = 1 then set
> cart_test.shipping_status to 'now' else set it to 'soon'
>
> UPDATE cart_test, products
> SET ca
My table products has ship_status INT, where it is either 1 or 0. I have
been moving those style fields to enum('now', 'soon') because it makes more
sense to me to be able to see the real values.
The problem is this is a live DB, and I am working on a dev site against the
live db, as much as I wa
