drawQuery performance...

[Paul james]

Thank you Ryan... That´s it !

So, I the steps are:
- queryByAttributes
- saveQuery
- drawQuery
...
- loadQuery
- drawMap

??

thx

On 5/4/05, Ryan, Adam <ARyan at co.linn.or.us> wrote:
> 
> Paul,
> 
> If I understand correctly, you have a query result that you want to persist
> in subsequent map.draw() calls.  Try using map.saveQuery and loadQuery.  You
> would save to a temporary file after your queryByAtributes and then load
> prior to each map.draw().  Is that what you're looking for?
> 
> Adam
> 
> 
> > -----Original Message-----
> > From: Paul james [mailto:pauljame at GMAIL.COM]
> > Sent: Wednesday, May 04, 2005 5:50 AM
> > To: MAPSERVER-USERS at LISTS.UMN.EDU
> > Subject: Re: [UMN_MAPSERVER-USERS] drawQuery performance...
> >
> >
> > Anyone could tell me, If I´m doing the right thing?
> > If I need execute drawQuery(so slow)  for each iteration with
> > map (to keep path selected) ?
> >
> > thx
> >
> >
> > ----- Original Message -----
> > From: "Paul james" <pauljame at GMAIL.COM>
> > To: <MAPSERVER-USERS at LISTS.UMN.EDU>
> > Sent: Tuesday, May 03, 2005 8:47 PM
> > Subject: [UMN_MAPSERVER-USERS] drawQuery performance...
> >
> >
> > In my project, I build a path with queryByAtributes(about 300
> > lines in result), and after I draw it with drawQuery... But
> > this function is a bit slow... And I must keep this path
> > selected, so I do the same process for each click in on map
> > (zoom, pan...) . Is this the best way to do it?
> >
> > Thank you...
> >
>