>From: "Steve Bernard" <[EMAIL PROTECTED]>
>
>URL identifiers "which most people won't notice", huh? Can you please let
>us
>know who you are working on shopping carts for, so that I can be sure never
>to use them?
>
>Steve
It works like this:
1. Form results to actionpage.cfm
2. Calculations then (cflocation to actionpage2.cfm?ID=whatever)
3. Calculations then (cflocation to action showresults.cfm) to show the
client the results.
The pages that do most of the work are hit with server side redirects. (And
before you ask, I had many reasons for two action pages.)
Even if someone goes through the trouble of tracing the URL's so what? The
only variable they'll see is worthless as far as getting any important data.
Crap, who cares what variables I'm using? All I'm trying to do is get some
help about how to fix this query caching problem, and I'm getting attacked
over my "lack of customer safety"?
If you can't help me with my problem, that's fine, but don't attack my
coding just because I used the dreaded "url.variable" on one page. I did
some things a slight bit different than you. So what? If you don't like the
way you "THINK" I code, fine. Don't jump on my case because you "THINK" you
see a mistake I'm doing.
Now back to the original problem, please.
> >Josh R wrote:
> > >
> > > PLEASE READ CAREFULLY
> > >
> > > (Technical info - Using CF 4.5.2 to query MS Access 97 SR2 database
>for
> >a
> > > text field and date field for unknown number of recordnumbers)
> > >
> > > OK. I have flushed the query by making a dynamically changing query
>name
> > > (I.E. cfquery name="shipments#uniquefield#") and made the page reload
> >using
> > > both unique html calls (I.E. updatecart.cfm?ID=#uniquefield2#") and
> > > (meta http-equiv="pragma" content="no-cache")
> > > (META HTTP-EQUIV="Expires" CONTENT="Mon, 06 Jan 1990 00:00:01 GMT")
> > > codes.
> > >
> > > It even loads itself into a second page with the exact same code with
> >all
> > > NEW uniquefields. There is no way (that I see) this query can get
>"old"
> > > data.
> > >
> > > BUT, that's exactly what it's doing. It grabs the data previous to
> >updating
> > > the database (even though the database has been verifyably updated
> >before
> > > this query.)
> > >
> > > I've even rewritten the query to see if it was just how the query was
> > > written. It still occasionally grabs "old" data.
> > >
> > > In short, grabbing this particular information sometimes grabs "old"
> >data
> > > instead of what is verifyably in the database.
> > >
> > > This problem does not occur on ANY other queries throughout the entire
> >site.
> > >
> > > Original Query
> > >
> > > (cfquery name="shipments#uniquefield#" datasource="mine"
>dbtype="ODBC")
> > > SELECT shipdate, shipmethod, Count(*) as totalCount
> > > FROM shopcart
> > > WHERE MyCart = '#url.cart#'
> > > Group by shipdate, shipmethod(/cfquery)
> > >
> > > Different Query asking for same
> > >
> > > (cfquery name="shipments#uniquefield#" datasource="mine"
>dbtype="ODBC")
> > > SELECT shipdate, shipmethod
> > > FROM shopcart
> > > WHERE MyCart = '#url.cart#'
> > > (/cfquery)
> > >
> > > Both Queries often come out with "old" data.
> > >
> > > Why is this data stuck? Why is this only happening with this info? Why
> >am I
> > > being tortured like this?
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
