Hi, From: ext Philip Van Hoof [[email protected]] Sent: 08 March 2011 14:55
[snip] > Some technical chitchat on this: [snip] sorry, I couldn't decide what to leave I believe I'm taking a _very_ different angle My proposal was: step 1: refer to the normal DB, as it is now step 2: should that fail, use the huge one The integrity/synch problem should be easy to address: * If the data in the first DB is more recent, it will be found during 1) * whenever the large DB is re-loaded, the smaller one can be refreshed (the time should be anyway acceptable _and_ it can be done when the device is unused, so it doesn't have to be lightning fast) Sorry if I'm blindly ignoring all the discussion about UNION etc, but I have the feeling that it is based on some requirement that has not been formulated addressing what are acceptable compromises from overall usability perspective. I do not know if there are other reasons why what I describe cannot be realistically implemented, but I would be quite happy if I could have something like that as an option. After all when I consult the physical white/yellow pages I do accept that they are not always up-to-date. cheers, igor _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
