fix(Migration): Don't use subquery

[marcelklehr]

No description provided.

[Copilot]

Pull Request Overview

This migration removes a subquery from a database update operation by replacing it with separate query execution and parameter binding. The change eliminates the use of createFunction() with a nested SQL query in favor of fetching IDs first and then using them as parameters.

• Replaced subquery pattern with parameter-based approach for better database compatibility
• Added explicit result handling with cursor management
• Introduced PDO import for fetch operations

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[nickvergessen]

Shouldn't you be able to update all with a single query?

Suggested change

	->where($query->expr()->in('id', $query->createParameter('ids')));
	->where($select->expr()->isNull('face_vector'));
	$query->executeStatement()

if you are not doing any data manipulation that should work just fine.
No previous select or anything needed.

[marcelklehr]

Shouldn't you be able to update all with a single query?

Doesn't seem work for large tables, sadly. See #1357

[nickvergessen]

Put a transaction around it?

[nickvergessen]

But anyway, should also be good like this, but it will run much longer.

But also in this version a transaction should speed up the update I think

[marcelklehr]

Mh, the issue in #1357 is due to a long running transaction, wouldn't wrapping the current state in this branch in a transaction introduce the issue of a long running transaction again?

[nickvergessen]

You can close the transaction after each chunk.
THe idea is to reduce the number of writes

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.