Identical Timed Session-Can Only Upload One

[BrianStaff]

Yesterday I did 3x15' pieces as per my Weight Loss Program and two of them came out to be exactly the same distance - consistent (although not spectacular) rowing I'd say

When I tried to upload my workouts via Logcard (6.10) it only uploaded one of them and the utility said the 2nd one was already uploaded. A brief look at what is happening is that a timed row is maybe identified by date (no time of day it seems) and distance only and so you can't have duplicates based on that criteria.





Model E with PM4 bought Feb 2008

Did I find a bug?

BTW - this posting is a duplicate of:

http://www.concept2.co.uk/forum/viewtop ... 70#p423453

Brian

[c2scott]

This is working as designed. Improvements to allow mutliple identical workouts on the same date are being considered, but I have no timeline for implementation of any changes.

[Citroen]

This is broken as designed.

So you've turned an obvious bug into a feechur.

[c2scott]

No, I would not characterize it as a feature, just a just a known limitation at the time the LCU upload feature was designed.

We could have employed many other methods...
- Allowing duplicates to be uploaded (boy would that have been a problem for people!)
- Marking the workouts on the LogCard as uploaded or not (but what if someone restores a card? What happens if they upload from a card image? What happens if the "mark" on the LogCard does not get updated properly?)
- Keeping a local database on the PC the customer is using (more complexity... and what if you use different PC's...)

The method that was chosen was to match duration of the workout (time, meters) and the date. If you look at the ranking, date is available for input but not time-of-day. There are just a handful of complaints or comments about this each year. We are looking to improve this in the future, but I'm dependent on the web/ranking team to design and implement changes on the database before we can move forward with something on the PC end...

[BrianStaff]

This is broken as designed.

So you've turned an obvious bug into a feechur.

Brian

[Citroen]

If you generated the verification code in the LogCard util would that be unique between the entries or is that only keyed off the date (and not time)? (I know you want to keep the algorithm behind that stuff secret, but the data in the XML would simply carry the same value that the PM3/PM4 generates.)

There's already the code behind the website to process that stuff.

[BrianStaff]

The method that was chosen was to match duration of the workout (time, meters) and the date. If you look at the ranking, date is available for input but not time-of-day. There are just a handful of complaints or comments about this each year. We are looking to improve this in the future, but I'm dependent on the web/ranking team to design and implement changes on the database before we can move forward with something on the PC end...

FWIW - I am a web database developer too, so I'm well familiar with the problem here. It seems to me that the issue relates to the workout session being kept in the database on the server does not have the Time-of-Day attached to it. If it did, then the problem is easy to fix. Most databases have a DATE data-type which allows a date AND time to be stored in one field. If that DATE data-type is already being used, then no database changes are required and the solution is to just populate the field with the full amount of data and apply logic to handle it. I understand though that it still requires modification on both ends - server & client.

Of course, if a DATE data-type is not being used, then that introduces added complexity to the problem.

Good luck - Brian

[c2scott]

Bottom line: it's a known missing feature and is on a long list of things to address....