I'm researching possibilities around the ATTACH DATABASE. For that I created db1.db and db2.db where both have a Table1 with the same schema. Db2.db also defines a view:

    CREATE VIEW Table1View AS
    SELECT *
      FROM Table1;

Then I leveraged sqlite3.exe to first open db1.db and then attached db2.db, which makes the db1.db a "least recently attached", and then finally executed:

SELECT * FROM Table1View

To see which table - Table1 from db1.db or Table1 from db2.db will be used to grab the data from the Table1 composing the view.

Reading this from the above doc:

If two or more tables in different databases have the same name and the schema-name prefix is not used on a table reference, then the table chosen is the one in the database that was least recently attached.

I was hoping there is a way to instruct SQLite to apply that rule not only against SQL commands issued on this specific connection with 2 active DBs but also against a view definitions.

Once the above SELECT from the view was executed, I saw the data was returned from the Table1 defined in db2.db, the same one defining the view, but not from Table1 defined in db1.db which was "least recently attached".

If, however, I execute on this same connection:

SELECT * FROM Table1

I do see the data from db1.Table1 is retrieved this time.

This tells me the table resolution described in the "ATTACH DATABASE" doesn't apply to a compiled View but instead only applies to a SELECT statements executed on this connection while explicitly referencing the table.

Is there a way to instruct the engine to apply the same resolution to a view's definition so db1.Table1 would sort of "override" db2.Table1 while Table1 is being accessed by the View?

The view lives in db1, so why do you expect it to select from a table from db2? I expect that if you create the same view in db2, that view will be chosen and return values from db2.Table1.

Not like I literally expect but rather I was wondering if that will take place after reading ATTACH DATABASE which states

If two or more tables in different databases have the same name and the schema-name prefix is not used on a table reference, then the table chosen is the one in the database that was least recently attached.

Especially after I proved that works if I issue explicit query

SELECT * FROM Table1View

then, in my case, I did see the data from db1 was retrieved. But, when, essentially, the same query was executed via the View, the data in db1.Table1 didn't override db2.Table1 and a data from Table1 belonging to the db2 was returned.

Note that some time ago creating cross-database views was prohibited (except for TEMP) ...

Does that mean NOW it is possible to create those views outside of TEMP?

If that is still possible only in TEMP, as I understand the view created in TEMP is only alive in that specific connection. I wonder if there is a way to somehow "persisted" those cross DB views across multiple application's restarts. Just in case want to re-iterate: I'm looking for a possibility to have a persisted (created not in TEMP) View composing tables from different databases.