Unfortunately it cause the #2311

FTR one used to be able to create a SqliteAdapter with empty options (e.g. for tests), but since this change at least the "name" option needs to be provided. I guess in the context of normal invocation that should always be set (cf. Phinx config environment section).

@InvisibleSmiley Just from reading the code, I think the previous behavior was that if no options was provided, then it'd create a file named .sqlite3, right? I'm wondering if there's a use for this outside of tests, and then for that, would it be fine to just have it default to :memory: if no options were set?

Though how hard is it to just mandate people use either name or memory option, and I feel like it's better to be explicit with how you want the connection to be setup vs relying on defaults.

I'm not saying anything needs to be changed, given that likely in real-world setups no-one actually instantiates SQLiteAdapter manually. If you consider that class to be internal, there is no need to even document the change in behavior/requirements.

Personally I would have had the code handle that case more gracefully, e.g. like this:

$name = $options['name'] ?? null;
if ($name === self::MEMORY) {
  return '';
}