Hi,
I have CF application which I have designed using verity search feature.
Overview :
The search application lets user search data in tables based of keywords and
the user could also filter by state or just say ALL ie. all states. I can
get results when search is based of ALL STATES since
Its stored in the client variable so I dont think its a client side cookie.
We use client variables that are stored in db for most of our applications.
If its a bad practice then we will create new thread as it might help me and
others. But at this moment my need is based on verity and how can i
Well, the data for the DB is something that is specific to the app,
not the client. Store it in the APPLICATION scope, not in the CLIENT
scope.
-dhs
Dean H. Saxe, CISSP, CEH
[EMAIL PROTECTED]
Dissent is the purest form of patriotism.
--Thomas Jefferson
On Mar 5, 2007, at 10:45 AM,
Yes, what you're suggesting
is a good idea, however, I would go a bit
further and place both Reason_Text and State
in that first custom field by simply delimiting
the data. Change the search page so that
if the user chooses a state other than all,
the following would be added to your
Change the search page so that if the user chooses a state other than all,
the following would be added to your Verity query: custom1 CONTAINS [state]
By verity query, do you mean the query which is used for building
collection? If it is, then dont you think it will be too much to index the
ok so for whatever reason (I'd rather not hear arguments why not to do
this) I want to try to do this:
cfset structVarName = myStruct /
cfset #structVarName# = StructNew()/
cfset keyVariable = steven.ross /
cfset theValue = a name /
cfset structVarName[keyVariable] = theValue /
the last part
Well I would want to ask and argue not to do this...but I'll bite my
tongue.
Why not create a superstructure to hold this. Then you could do
something like:
cfset superstruct=structnew()
cfset structVarName = myStruct /
cfset superstruct[structVarName] = StructNew()/
cfset keyVariable =
thanks! this worked:
cfset variables.structVarName = myStruct /
cfset #structVarName# = StructNew()/
cfset keyVariable = steven.ross /
cfset theValue = a name /
cfdump var=#Evaluate(structVarName)#
cfset variables[structVarName][keyVariable] = theValue /
cfdump
My whole suggestion
about combining State and Reason_Text in
one custom field, was so that you wouldn't
have to sacrifice the Reason_Text
Without trying to understand
too much of your query...
step 1: run query
SELECT field1, field2,
..., Reason_Text + "|" + State AS
You can also use the SetVariable function if you wanted to avoid the
syntax magic of cfset #var# = some value.
Jeremy
On 3/5/07, Steven Ross [EMAIL PROTECTED] wrote:
Ok I'll let you in on it... heh. Ok so I have a configuration xml file
and I want to be able to dynamically create structs and
Hello everyone,
It was great learning stuff today. Let me recap
1) Thanks Dean for pointing out not to store dbname in client var and
instead store in appl var
2) Mischa, your input really got it all started. As per your last email, I
have made some changes and I think
11 matches
Mail list logo
