I am guessing whatever you are trying to do could be accomplished in sql in
a much more elegant solution... might be wrong but, that would be worth
investigating as well.
On Wed, Nov 2, 2011 at 7:00 PM, Charlie Arehart wrote:
> Consider also Matthew that it may be helpful to output the autoorders
Consider also Matthew that it may be helpful to output the autoorders as
well for debugging purposes. It, too, may not be what you expect.
For instance, if this code is in a CFC method, then you could be having a
situation where other requests are causing conflicts with the variables. If
you've n
First this I see is to try scoping your "id" var:
If the value of "id" is remaining the same as the first query value, then
it's always going to return 1 as the list position.
You can also output the id value and it's list "pos" as a debug measure if
you want... Either inline or using cflog or
I'm always happy to share an example of bad practices! :D
All things said and done this solution is far from ideal, which is an
understatement, but I'm always excited to hear options and opinions.
>From a high level, this is the current process outlined below in code:
1. Stored Proc
First, as to your actual problem with listFindNoCase() returning 1, I'd say
show your code. There could be a number of logic problems causing this.
However, I think you are going to run into another problem first. Because
of the way CF handles lists, it's a real REAL bad idea to keep long lists
Morning All!
I could swear we had a discussion about this awhile ago (although I may
just be remembering an article from Charlie's site).
I'm experiencing a bit of a head scratcher in regards to lists and
managing them.
1. Using a QoQ, we create a ValueList from one of its columns
