INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: 1 [2]   Go Down

Author Topic: 'Saving Database' excessively, resource hog  (Read 10365 times)

nila

  • Guest
Re:'Saving Database' excessively, resource hog
« Reply #50 on: December 01, 2003, 07:11:13 am »

It could also lead onto a History option (in the AW - like in Photoshop) so that changes could be viewed (previously done and ones to be done) and individual actions could be undone etc.

Would BLOW all the other jukeboxes out the window.
Logged

KingSparta

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 20062
Re:'Saving Database' excessively, resource hog
« Reply #51 on: December 01, 2003, 07:31:45 am »

Quote
You could easily narrow down the window of opportunity for loosing any changes by logging the details of the change to a permanent file instead of holding them in memory.

yes i was thinking of that my self

or if there was a way to directly access the database for that file make the changes to that data field only.

I am guessing the database type does not support this however.
Logged
Retired Military, Airborne, Air Assault, And Flight Wings.
Model Trains, Internet, Ham Radio, Music
https://MyAAGrapevines.com
https://centercitybbs.com
Fayetteville, NC, USA

nila

  • Guest
Re:'Saving Database' excessively, resource hog
« Reply #52 on: December 01, 2003, 07:46:14 am »

King, the problem comes from tags written to the files themselves.
The db tagging for me at least is pretty good. Full credit for the speed of it to the whole team.

Rhino's way would speed it up a LOT more though for tags saved in the actual files when several changes are made.
Logged

RhinoBanga

  • Citizen of the Universe
  • *****
  • Posts: 1703
  • Developer
Re:'Saving Database' excessively, resource hog
« Reply #53 on: December 01, 2003, 07:47:51 am »

Especially if you group changes by file to also take advantage of OS caching.
Logged

KingSparta

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 20062
Re:'Saving Database' excessively, resource hog
« Reply #54 on: December 01, 2003, 08:01:11 am »

King, the problem comes from tags written to the files themselves.
The db tagging for me at least is pretty good. Full credit for the speed of it to the whole team.

Rhino's way would speed it up a LOT more though for tags saved in the actual files when several changes are made.

So you think it's not the database but writing to the ID3 tags.

well the way it is now many times you need to go back and save the same file with a new change, the changes matt did before (not the speed of the database changes) he said was to keep the tags from being written. but the only thing i see is many pop ups asking me if i really want to do the save (reminds me of pop-up ads really), and then i have to make more changes after it saves.

all of this pop-up warnings could be avoided if each file had a way to undo the changes (but thats another subject).



Logged
Retired Military, Airborne, Air Assault, And Flight Wings.
Model Trains, Internet, Ham Radio, Music
https://MyAAGrapevines.com
https://centercitybbs.com
Fayetteville, NC, USA

nila

  • Guest
Re:'Saving Database' excessively, resource hog
« Reply #55 on: December 01, 2003, 08:31:11 am »

It's two fold really :)

The DB issue Lise originally mentioned and also the pain when trying to tag alot of files and having it stopping you after each group of changes instead of being able to just wait till the end of tagging them fully before applying all the tag changes.
Logged
Pages: 1 [2]   Go Up