Hello Richard !
Looking at the documentation, code and code comments I found that what
I'm looking for somehow already exists in sqlite3, I mean I want the
functionality of "temp" database as permanent let's call this database
as "meta" anything created inside "meta" database would persist on
On 10/5/16, Domingo Alvarez Duarte wrote:
>
> I just found that the changes I made to sqlite3 to allow reference
> objects on attached databases does not work properly,
>
> Where in the view execution path the table/view qualifiers could be
> discarded ?
>
I'm not sure exactly what you are lookin
Hello Richard !
I just found that the changes I made to sqlite3 to allow reference
objects on attached databases does not work properly, it does work when
the tables/views from more than one database are not equal but if they
are equal even with qualification it seems to always try to find fir
Hello Richard !
Thanks for reply !
I found the second point that was also controlling the restriction of
referencing objects in other databases.
Now it seems to work and I'll leave the initialization to the user level
code for now, when the usage normalize I'll revisit it again to see if
is
On 10/4/16, Domingo Alvarez Duarte wrote:
>>
> The problem is I didn't found yet the point where I should intercept the
> "openDatabase" where I plan to check if there is a table named for
> example "use_attached_dbs" and then attach the databases on that table
> and then reread the schema to make
Hello !
I'm trying to make changes to sqlite to allow multi-databases databases
(I mean have a database that is onl used to anchor attached databases
and store mutli-database views/triggers).
I already managed to add a new pragma "use_attached_databases=ON/OFF" to
allow views/triggers to hav
6 matches
Mail list logo