29 Oct 16:18
Re: memory consumption problem as collections get bigger
2008/10/29 Robby Stephenson <robby-9lFPeden07UgsBAKwltoeQ@public.gmane.org>
If you can create a model in Django, then you can generate the SQL tables from the code Django creates, and have a first tool to edit it (the Django admin module). Once you have the database tables correct, well, I suppose the real work only starts then
Benny
Benny Malengier wrote:2008/10/29 Robby Stephenson <robby-9lFPeden07UgsBAKwltoeQ@public.gmane.org Tellico holds all the collection data in RAM once the file is
opened. That's
obviously not going to work well with really big collections, it's
just the
way I wrote it. If you delete your data file once it's loaded,
Tellico can
save it again completely.
If things are in an sqlite embedded database as eg Amarok collection, you can avoid this. Undo is possible by going back in the database logs. Anyway, with all the database based apps now, people get used to atomic saves in apps that handle collections
True. I wish I spoke SQL. I've taken a shot at it before, and had problems getting the performance.
If you can create a model in Django, then you can generate the SQL tables from the code Django creates, and have a first tool to edit it (the Django admin module). Once you have the database tables correct, well, I suppose the real work only starts then

Benny
_______________________________________________ tellico-users mailing list tellico-users@... http://forge.novell.com/mailman/listinfo/tellico-users
RSS Feed