Skip to main content
June 22, 2006
Question

Yet Another 8.0.2 bug

  • June 22, 2006
  • 2 replies
  • 202 views
With 8.0.2 (at least with PHP/MySQL) you can no longer use a variable in your custom SQL more than once. You must specify "duplicate" variables. For example - I want to find all records where either SCORE is equal to a passed URL parameter or PLACE is equal to the same URL parameter. This will NOT work anymore:

SELECT * FROM mytable
WHERE score = varTheParam OR place = varTheParam


Define your varTheParam, try to test the results and you get yelled at because varTheParam is undefined. Your SQL must be like this:

SELECT * FROM mytable
WHERE score = varTheParam OR place = varTheSameParamAgain


Now, define your varTheParam and varTheSameParamAgain - setting them both equal to the same thing. A waste of resources here.
This topic has been closed for replies.

2 replies

Inspiring
June 22, 2006
Come on 8.0.3 update....or just reinstall 8 and not the latest update. :-)




"Tom Muck" <tommuck@NOSPAM.basic-drumbeat.com> wrote in message
news:e7eida$bcf$1@forums.macromedia.com...
>
> "abtech123" <webforumsuser@macromedia.com> wrote in message
> news:e7ei9g$b3s$1@forums.macromedia.com...
>> With 8.0.2 (at least with PHP/MySQL) you can no longer use a variable in
>> your
>> custom SQL more than once. You must specify "duplicate" variables. For
>> example
>> - I want to find all records where either SCORE is equal to a passed URL
>> parameter or PLACE is equal to the same URL parameter. This will NOT work
>> anymore:
>
> Good catch. Just another in the long list of severe recordset bugs in the
> 8.0.2 updater.
>
> Tom
>


Inspiring
June 24, 2006
I was wondering what was going on with these variables. Least there's a work around.
Inspiring
June 22, 2006

"abtech123" <webforumsuser@macromedia.com> wrote in message
news:e7ei9g$b3s$1@forums.macromedia.com...
> With 8.0.2 (at least with PHP/MySQL) you can no longer use a variable in
> your
> custom SQL more than once. You must specify "duplicate" variables. For
> example
> - I want to find all records where either SCORE is equal to a passed URL
> parameter or PLACE is equal to the same URL parameter. This will NOT work
> anymore:

Good catch. Just another in the long list of severe recordset bugs in the
8.0.2 updater.

Tom