Import PQ Name in DB by sbeelis - 2013-09-04

QUOTE (Kai Team @ September 03, 2013 10:52 pm)

QUOTE (HHL @ September 03, 2013 07:10 am) I know about that GS feature. But that doesn't change the issue with the long path names. Agreed - the feature would be better with just the file name, not the path. Image may be NSFW. Clik here to view.

+1

Even though I voted that I would rarely use this feature, I've added the custom field and (thanks to already having set the PQ name as part of the file name on all my PQs) immediately saw which of my date-range PQs updated which cache. It then occurred to me that this could be a good way of identifying "stray" caches that due to sloppiness in the date ranges fall between two PQs, so I really find this feature very useful.

Having the file name only would make this much more useful, yet.

And maybe an option to not write the field when doing an API refresh as "refresh0.gpx" is not all that helpful, especially when it overwrites the PQ name that I'm really interested in.