`(sqlite3.OperationalError) too many SQL variables` exception

[GeigerJ2]

When doing an import dry-run of the MC3D provenance archive to an sqlite_dos profile via: verdi archive import MC3D-provenance.aiida -n I just got the following exception:

╰─ verdi archive import MC3D-provenance.aiida -n
Report: starting import: MC3D-provenance.aiida
Report: Parameters
-------------------------------  ---------------------
Archive                          MC3D-provenance.aiida
New Node Extras                  keep
Merge Node Extras (in database)  (k)eep
Merge Node Extras (in archive)   do (n)ot create
Merge Node Extras (in both)      (l)eave existing
Merge Comments                   leave
Computer Authinfos               exclude

Report: Test run: nothing will be added to the profile
Report: Adding 1 new user(s)
Report: Adding 3 new computer(s)
Report: Re-labelled 2 new Computer(s)
Report: Collecting Node(s) ...
Critical: an exception occurred while trying to import the archive MC3D-provenance.aiida: OperationalError: (sqlite3.OperationalError) too many SQL variables
[SQL: SELECT db_dbnode_1.uuid, db_dbnode_1.id
FROM db_dbnode AS db_dbnode_1
WHERE CAST(db_dbnode_1.node_type AS VARCHAR) LIKE ? ESCAPE '\' AND db_dbnode_1.uuid IN (?, ?, ?, ... 
...<question marks repeat>...
?, ?)
(Background on this error at: https://sqlalche.me/e/20/e3q8)

The command ran fine through for an psql_dos profile.

(Not sure if #5740 is somehow related)

[sphuber]

The source of the error is exactly what #5740 addressed. While importing, a query is made to check what nodes to be imported already exist in the target storage, and this leads to many parameters, which exceeds the statically defined limit. What I don't fully understand yet is why this was not caught by the mentioned PR. Will have to find the exact line that throws this exception to see why that is not getting batched.