> Well, I love sqlite, and I want to continue using it (small, fast, > reliable ...). > I think it is better to solve such problems inside sqlite
It's impossible. Just try to design the solution you want. Think of how SQLite should behave to make you happy, think of it with all details and don't forget that SQLite is a library living inside several processes simultaneously, sometimes even on different computers (although it's discouraged), those processes can crash unpredictably and you have to manage all crashes predictably. So if you are able to come up with some solution and post all technical details here I think SQLite developers will be happy to implement it. Pavel On Sun, Nov 28, 2010 at 3:19 AM, Yoni Londner <[email protected]> wrote: > Hi, > > > For a large scale system you have a third choice: use some other RDBMS > > which is implemented in one process and has a much better control over > > its data and much better communication between readers and writers. > Well, I love sqlite, and I want to continue using it (small, fast, > reliable ...). > I think it is better to solve such problems inside sqlite (Not to > mention you don't need large scale system to reproduce this issue, 50 > lines of C code is enough). > > Yoni. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
