Conflicting Database.logError ? about grdb.swift HOT 3 CLOSED

Hello @gmoraleda,

The SQLite Error And Warning Log is global: it captures SQLite errors from the whole process.

The callback just gets an error message and an error code. It does not know which SQLite connection is the source of the error: it is impossible to distinguish the databases you create from databases created by third-party libraries or the system, from within the process of your application.

This SQLite tool is documented as a "huge aid for debugging", so I'm not sure that the captured "noise" would be considered as an issue by SQLite authors. They could argue that in this noisy signal is the information you are looking for when you are debugging, so the main use case remains well-addressed. Maybe you can discuss this topic in the SQLite forums, though. You could argue that modern applications can use a lot of SQLite databases, and that the noise is becoming too high.

I'm sorry iOS 17.2 has introduced more SQLite-based libraries that trigger SQLite errors, but there's nothing GRDB can do in the current state of SQLite.

from grdb.swift.

That makes a lot of sense.
Thanks a lot for your comprehensive reply @groue!

from grdb.swift.

You're welcome! Happy GRDB :-)

from grdb.swift.