Hi list!
I'm developing an open source project (a Data Access Grid) that
uses internally the SQLite library as the storage method and I'm
interested in your opinion about 4 questions:
1) SQLite can't deal with raw devices. Should be hard to patch the
source to deal with raw devices?
2) SQLite doesn't have support for views envolving multiple databases.
In example:
sqlite> attach 'test.db' as db2;
sqlite> create table db2.t1 (c1);
sqlite> create view v1 as select * from main.t1 union select * from
db2.t1;
I have a patch that works for me but the engine have problems when doing
a VACUUM if the other involved databases are detacheds and the unique
solution is to re-ATTACH the other involved databases.
I tried also to do the same with triggers (triggers that involves
multiple databases) but it appears to be hard. What can I do?
Attached goes patches to make working views envolving multiple
databases.
3) I want to write an stored procedure engine (such as Pl/PgSQL, Pl/SQL,
etc...). Is anyone working on something like this?
4) I have an idea about what can be done to get working a page level
locking to replace the database level locking. Currently SQLite has only
support for database level locking. My idea should works on POSIX based
systems. Why not use mmap, munmap, mprotect, mlock, etc... system calls?
Regards,
Joxean Koret
264a265 > #if !defined(SQLITE_ALLOW_MULTIDATABASE_VIEWS) 271a273 > #endif
134a135,142 > ** Can we create views that involves other databases different than > ** the main database? By default this is not allowed but, in our probes, > ** this doesn't cause any kind of problems except that you need to attach > ** the database in which the related objects are. > */ > #define SQLITE_ALLOW_MULTIDATABASE_VIEWS 1 > > /*
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
