Jump to content

PQ start date is NOW non-inclusive? Why?

LeGodFather

By LeGodFather
in Website

Followers 3

Recommended Posts

LeGodFather

+LeGodFather

Posted
Posted

Pocket Query start date use to be "inclusive".. meaning that a PQ selecting caches placed during , between October 13 2007 and October 14 2007* would return all caches with a "placed date" of "10/13/2007" and after and before "10/14/2007" including caches placed on "10/14/2007".

 

Now, a PQ with the same dates as in the example above.. return only the caches with a "placed date" AFTER "10/13/2007".. excluding caches placed on the 13th.. the starting date of the PQ (so, only the caches placed on the 14th, in my example).

 

Sounds like a "greater or equal" was changed to a "greater than" (or something like that).. is that something wanted? Requested? or what?

 

* Also, we use to be able to select the years beyond the current year. Now, we are stuck making PQs end at "Decembre 31 2007". Events are placed in the future.. and I like to have a PQ that checks the next three months for new events!

 

Thanks for reading.. ;)

The Leprechauns

+The Leprechauns

Posted
Posted

Posting to confirm that caches hidden on the first day selected in the "between" date field on my date-ranged pocket queries are NOT being returned in the pocket query files. Please let us know whether to edit our date-ranged queries, or if the pocket query generator will be fixed to function as before. Thanks!

markandlynn

markandlynn

Posted
Posted

Posting to confirm that caches hidden on the first day selected in the "between" date field on my date-ranged pocket queries are NOT being returned in the pocket query files. Please let us know whether to edit our date-ranged queries, or if the pocket query generator will be fixed to function as before. Thanks!

 

Ditto my pq's are all broken now ;) i know from the number of downloads of my paperless caching guide that its broke for a lot of people who wont realise until they see that long list of waypoints not updating in gsak. :yikes:

Stunod

+Stunod

Posted
Posted

Another confirmation here...

 

Guidance on whether to edit our PQ's would be greatly appreciated. I know there are a lot of people who use date ranges on PQ's to cover larger areas without overlap who are affected by this.

 

Thank you GrosseFamille for catching this change...

purple_pineapple

+purple_pineapple

Posted
Posted

Another confirmation here...

 

Guidance on whether to edit our PQ's would be greatly appreciated. I know there are a lot of people who use date ranges on PQ's to cover larger areas without overlap who are affected by this.

 

Thank you GrosseFamille for catching this change...

 

On the other matter as well, surely it is important that we can select dates beyond 2007? The UK (as I'm sure does the rest of the world!) already has several events listed for next year, and it would be rather helpful to actually receive them!

 

here's hoping someone accidentally put the wrong bit of code in somewhere..!

LeGodFather

+LeGodFather

Posted
  • Author
Posted

I'm glad that I'm not the only one that sees this!

 

Thank you all for confirming the problem.. or er.. the change!

 

I think it would be appreciated by everyone if someone from Groundspeak could chime in with more details..

Isonzo Karst

+Isonzo Karst

Posted
Posted

It's early Monday morning yet in Seattle WA where most of the Groundspeak staff live.

This seems like an unintentional development, certainly it requires that every date ranged PQ be rewritten, I'm optimistic that it will be addressed.

trainlove

+trainlove

Posted
Posted

Arggh!!! Thanks for the heads-up :mad:

 

How many PQ set-ups will that break?

 

Please, Groundspeak, can you fix this one as soon as possible!!

 

I think it will break ALL of the PQ's that use dates since most people who use dates do so in such a way that PQ1 gets you A, PQ2 gets you B after A, PQ3 gets you C...

I know 25 ogf mine are broken, but

baloo&bd

+baloo&bd

Posted
Posted

Maybe I am the only one, but I got 4 PQ's this AM, all based on placed date, and did not see this occur.

 

3:09

3:29

3:55

3:56

 

All central time.

 

When I checked them, all the dates were included.

Alan White

Alan White

Posted
Posted

I don't want to be a wet blanket but I don't think it has been fixed.

 

If I look for caches placed between 12th Oct and 13th Oct I get a list of caches placed only on 13th. If I look for caches placed between 13th Oct and 14th Oct I get a list of caches placed only on 14th. If I look for caches placed between 14th Oct and 14th Oct I get none.

Stunod

+Stunod

Posted
Posted

I don't want to be a wet blanket but I don't think it has been fixed.

 

I concur. My test PQ for a 2 day range (10/14-10/15) is only returning 10/15 results. If I expand the range to 10/13-10/15, I do get 10/14 results (but no 10/13)

trainlove

+trainlove

Posted
Posted

I just might have to re-suscribe to a Premium Membership to update my New England by date PQ's.

And to test this problem.

 

I am unsure if the prior runs I've done had any holes between the end of 1 PQ and the start of another. Or perhaps I'll just have to bite the bullet and have some overlap and therefore have even more slightly less that 500 results per PQ.

I.E.:

Mass1, all unfound by me, 01/01/2000-06/09/2003

Mass2, all unfound by me, 06/08/2003-09/15/2004 (not 6/9 or even 6/10 as I had previously defined it)

...

...

...

 

Oh, these are random dates. Since I'm not currently a Premium Member I can't even look at the previously defined PQ's.

 

One good thing though, since I only PQ unfound caches each time I ran these queries I would adjust all the dates forward until I get just under 499. And in a few cases had to adjust a date backwards when a whole slew of temporarily archived caches became available again.

Haffy

+Haffy

Posted
Posted

Don't change anything. I'll find out what happened and make sure it's reverted back to the way it was.

 

He was referring the this reply so don't change a thing just yet,give em time.

Stunod

+Stunod

Posted
Posted

Don't change anything. I'll find out what happened and make sure it's reverted back to the way it was.

 

He was referring the this reply so don't change a thing just yet,give em time.

 

I didn't listen to his advice and changed the dates in my PQs.

 

Worst case I get duplicate results...

LeGodFather

+LeGodFather

Posted
  • Author
Posted

This was 4 days ago. Meanwhile we are getting incomplete data. :surprise:

My thoughts exactly.

 

Maybe I expect too much because I work in an IT world where we have to give updates every 2 hours when there is a problem. We're just asking for an update.. every 2 hours is probably too much in this case.. maybe every 2 days?

 

Anyways..

LeGodFather

+LeGodFather

Posted
  • Author
Posted

It's Friday, and I got all my PQs for the week. And, it looks like it was only the "Preview Pocket Query" lightning_go.png that was not returning the caches placed on the first day of the PQs dates.

 

And.. I've just ran (3 times) a "Preview Pocket Query" lightning_go.png and it looks (once again) like it has been fixed. It does show the caches of the first date.

 

Anyone can confirm this?

 

I'm happy with what I have now. Thank you! :surprise:

The Leprechauns

+The Leprechauns

Posted
Posted

Thank you to those confirming that the issue has been fixed. My home area date-separated pocket queries run from Monday through Friday so I can use them over the weekend. As my bad luck would have it, I updated the queries last weekend, not knowing of the site issue. So the settings are quite messed up, but now I know that I can fix the date ranges again. Only a subset of the cache data was affected, and for a very short period. The majority of caches in my queries update with new activity less often than weekly.

Guest
This topic is now closed to further replies.
Followers 3
Go to topic listing
×
×
  • Create New...