On 08/03/11 11:58, [email protected] wrote:
Hi,
Hi Igor,
From: ext Martyn Russell [[email protected]]
Sent: 08 March 2011 13:53
As you can imagine, if you want to be able to query, insert and merge
120k of contracts, you really can't have your cake and eat it so to
speak without some sacrifices one way or another.
That's not true.
Nothing prevents from having 2 DB, where the first one is the usual (could be
considered as cache)
and the other is much larger and used only in case the first search fails.
Maybe with the explicit consent from the user to proceed with such
expensive operation.
We have also considered this or "views" and it is something we've got in
mind to investigate more thoroughly, but NOT as separate databases).
But as you say, you then have a sync issue to deal with and this syncing
is EXACTLY the problem application developers report to us and don't
want to see. For example, you create an image and want the image to be
in the database instantly so you can query on it, but you're still
writing the file to disk at the time. The latencies and race conditions
here are nasty for application developers and your double DB solution
really doesn't help there.
Also, we've had > 1 DB before in Tracker and it was a nightmare. There
are problems with joins, security, speed, etc. and we've (as a team)
discussed this so much already. We have also done testing with n
databases vs 1 database to make sure that our approach makes the most
sense with SQLite as it also depends on which database you use.
--
Regards,
Martyn
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
