Backup MM Tracks v2.7 (01-11-08) [MM3]

[MoDementia]

How did I know that was coming

[nynaevelan]

How did I know that was coming

Because you have been writing scripts for me long enough to know I am going to push for one step more.....

Nyn

[MoDementia]

New Version

' Faster Create Directory Code
' 15-09-08 Version 2.3
' Fixed Shorten Path/Filename not working (Regression)
' Added Moved tracks to Missing Node (Missing/Moved)
' New Node Tracks changed since last backup

[nynaevelan]

' Faster Create Directory Code

The difference in speed is very noticable.

' Added Moved tracks to Missing Node (Missing/Moved)

Thank you, although the problem was more problematic than I thought, it found over 1300 tracks that are "missing".

' New Node Tracks changed since last backup

I like this new feature, although a downside is, since it is a new version it recognizes the entire library as "changed". Not a problem though, I will rebackup all the tracks while I am at work. So from now on I should be able to see some real results.

Once again, thank you for your assistance in helping me.

Nyn

[nynaevelan]

There is something wacky going on with the Tracks Changed Since Last Backup Node in v2.3. I have spent the last few days using v2.2 to rebackup all my tracks. After I finished, I updated to v2.3 and now the node says 10091 of my 11792 tracks have changed. That is absolutely impossible. Do you have any ideas what could be causing these discrepancies? This cannot be a question of a restoration of a previous backup because I just finished backing them up so there should be no changes because other than playing some tracks, there were no other changes. If you need to see a copy of my db, you can download from the usual spot.

Nyn

[MoDementia]

Does 79 sound about right ? 8 decimal places

[EDIT]
Or maybe 623 ? 9 decimal places
Or maybe 404 ? 10 decimal places wtf?

or maybe 9348 12 decimal places

It depends on how many decimal places I round TrackModified off too

[nynaevelan]

79 and 404 would be closer but I don't think either is right. I've played 189 tracks in the last two days and that is the only thing I've done in the db in the last two days.

Nyn

[nynaevelan]

The Songs table has 10 decimal places, maybe BMT should stay at 10? I could live with 404 better than 10091.

Nyn

[MoDementia]

The Songs table has 10 decimal places, maybe BMT should stay at 10? I could live with 404 better than 10091.

Nyn

That's the problem even though you can only see 10 decimal places it actually has infinite

I might give Bex a go at it there maybe a better way than rounding

[Bex]

@Mo

The solution is to CAST(Datefield as TEXT) before you compare them in the SQL. That way you don't get the differences that REAL fields sometimes give.
(Unless I'm missing something here.)

[MoDementia]

@Mo

The solution is to CAST(Datefield as TEXT) before you compare them in the SQL. That way you don't get the differences that REAL fields sometimes give.
(Unless I'm missing something here.)

Lucky I checked back before I finished the PM

Code: Select all

  SDB.MainTracksWindow.AddTracksFromQuery("WHERE Cast(Songs.TrackModified as TEXT)<>(SELECT Cast(TrackBackup.TrackModified as TEXT) FROM TrackBackup WHERE Songs.ID=ID)")

Gives 79 Tracks

Unless there is something else wrong with the SQL then it's as close as I can get it

If it's wrong I guess I just have to take it out

[Bex]

That should do it!

But I think this sql is faster:

Code: Select all

SDB.MainTracksWindow.AddTracksFromQuery(", TrackBackup WHERE Songs.ID=ID and CAST(Songs.TrackModified AS TEXT)<>CAST(TrackBackup.TrackModified AS TEXT)")

[nynaevelan]

Ok, this is a lot closer but the only thing that has changed with these tracks is the play info, is a backup necessary just because the playcounts have been updated? What is the difference between the TrackModified and FileModified fields? My understanding is the FileModified is the actual file and TrackModified is what is in the db, am I misinterpreting? If not, wouldn't the FileModified be a better field to compare to? I really do want this node but I don't want to have to perform a backup each time I play some tracks.

Nyn

[MoDementia]

Thanks Bex.

My understanding is the FileModified is the actual file and TrackModified is what is in the db

This is true and correct

I was initially going to use FileModified but for reason(s) I can't remember now, I decided against it.

It may have been that people can turn the update of filemodified off or that changing directories doesn't change the filemodified date or something
I can't remember

It would take some convincing to change it back because what I do remember is that it was a pain when I discoverd some things didn't trigger the filmodified value

[nynaevelan]

I understand your reluctance, but is there a way to use TrackModified without the playcounts showing up as changed tracks? If not, the node doesn't work for me because I would be backing up everyday....

Nyn