Rob Shortt wrote:-You must load the schema into the database before using it, sqlite /path/to/freevo/cache/epgdb < lib/pyepg/epg_schema.sql. I would like to have this automaticly done, and also a way to auto upgrade the schema between revisiions.
IIRC Aubins metadata db doesn't need this. Maybe you can look there.
Yep, saw that. At first I was partial to keeping the schema defined in a single file.
-It still takes too long to enter the guide. Its fast getting the programs form the database but I'm still creating a ProgramItem for every program in the guide. We could: 1) get smaller groups of programs at a time, 2) have something refresh our data in the background, 3) don't keep a persistant list of ProgramItems but rebuild them on a page by page basis by creating them on the fly from frequent DB queries.
2 is the way to go. Look at listing_area.py. For thumbnail listing (image view) the area loads the next menu in background using the notifier callback. One image at a time to make sure it won't stop freevo. 3 is bad, I guess it will be too slow. But maybe combine 2 and 3 like the listing. Get the complete data on guide startup (should be fast), create items for the needed ones and load the next page in each direction in background.
Ok, I will play with that and see what I come up with thanks.
-do we still need to create an index of the list of ProgramItems for faster access?
No, it was a hack for the tv guide for faster access. I don't think we
still need it.
Ok, I'll remove that and see what happens.
-how should we deal with empy data and gaps? Should we use ProgramItems with defaults suitable for manipulating in a manual record interface (30-60 minute chunks)?
Sounds ok. BTW, when you get a new data for lets say Monday and you already have Monday. Do you merge the data or do you replace?
Right now I update if its there and something changed. I am working on a scheme to detect if a program's start and stop have shifted, or the program was removed from the real schedule. I geuss I'll address this on the list when I get back to it.
-Unicode: I think sqlite uses unicode, do we have to change anthing with how we deal with unicode with regard to the DB?
No, I hope Freevo is 100% unicode now (except filenames).
Ok, that's good.
-Rob
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel