Saving every activity

[Jaymz]

When I close the program and ask to 'Save' the activities it looks like it saves all of them again. Is that right? Should it only save the changed ones?

Seems that once you log some serious amount of activities it is going to start to take a while to save doing it that way.

[stevek]

I have over 800 activities, it does take a long time, as does manually adding activities.

Add onto that the complete back up to a local drive and on to mobile me, closing Ascent is beginning to take a long time.......

As Jamz says is there not a way to only save new or changed data?

Steve

[oshloel]

This issue also affects the time it takes to launch Ascent. I currently have about 700 activities, many with 1 second recording, in a 95+MB file and I find launching to be a more irritating wait than saving. It's an issue that Rob has on his list to address, but apparently will require a complete re-engineering of the underlying database and so probably won't happen until a major version upgrade.

In the mean time, a workaround I likely will use is to split my Ascent file into several files, one for each year or so. That's not as nice as one big file, but it's still relatively easy to compare data since you can have more than one Ascent file open simultaneously.

Rick

[Jaymz]

Good idea. Is it possible to merge these files afterwards?

for example. If I started a 2010 file could I, say every month or two, merge that 2010 file in with my 'all encompassing' training file that contains all of the years? Still keeping the 2010 file separate for regular opening and closing but also maintaining an all round file?

[Jaymz]

If Rob was to work on it tonight he could have it ready by morning and that would mean at least three of us would be happy

[rob]

re: merging

You can easily keep a file of all activities, as well as the most recent subset (the current year for example). The best way to manage this would be to normally sync into the current document, then periodically open the "all" document, go back and select new activities in the current document and copy them to the paste buffer (CMD-C), then return to the "all" document and paste in the new activities (CMD-V)

re: load/save times
As Rick said, the underlying database needs a re-organization to speed this up for very large files. It's on the list -- unfortunately more than a night's work...

[i-Mac]

Maybe a simple solution .... Make a new database for every year.

[rrooster]

I believe the ultimate solution would be for Ascent to be built on top of a relational data base which is always dynamically updated when a change happens and needs no physical "save" to be selected... reminiscent of 1Password, Accounts, and many other apps on the Mac OS X platform.

However... that's a big redesign, which I hope comes sooner than later... as more and more app features make this database redesign more and more onerous.

In the mean time...

1.10.4 has a problem that when a save happens, a dark dot is showing in the Green Icon on the top left of the window... this is characteristic of a file, which is open and has NOT been saved.

r

[Mick F]

In the mean time...

1.10.4 has a problem that when a save happens, a dark dot is showing in the Green Icon on the top left of the window... this is characteristic of a file, which is open and has NOT been saved.

r

Not on mine, it doesn't!
I suppose you mean a dark dot in the RED icon, but one is only there if any changes have been made ........ as it's supposed to be.

[rrooster]

opps — yes - RED icon... I'm using the Graphite setting... so in a sense, I'm colour blind. — Sorry for the confusion.

I've attached a screen shot of what I get SOMETIMES after saving... (it's not happening every time)


r

[strayduck]

So I had just imported three recent rides into Ascent and added some temperature notes and went to quit out and saw this:



...this was an event from 6 months ago which I wasn't anywhere near during this session. I am guessing this is part of the problem of the single database listed in this thread.

I'd like to echo the request for the splitting of events despite it being a large chunk of engineering. Learning that our life on our bikes is sitting in one file makes me very nervous -- it reminds me of Outlook email where ALL of your calendar, contacts and email data is in one proprietary (and highly corruptible) database. One failure can bring the whole thing down and *poof* there goes your life. Extending the email analogy a step further: your smart email programs such as Mozilla Thunderbird and Apple Mail store each email message as it's own discrete file so a corruption of one does not affect all others.