Is it possible to get the log written by the logStatements flag?

[madsane29]

I am trying to implement logging in my app and it would help if I could somehow get the DB logs written by Drift...

I write my own logs as well and save it in the DB so the customer can send these logs to me in case something wrong happens...

[simolus3]

The easiest way to do this is to override driftRuntimeOptions.debugPrint with your custom logging function.

[madsane29]

By any chance is there some example how am I supposed to override classes like these? I tried in several ways but can't really find the solution.

Thanks in advance.

[simolus3]

Reading this again, I think I may have completely misunderstood your question. Do you want to store log messages in a drift database? I'm happy to help you with that, I just assumed you wanted to get logs for SQL statements executed by drift. Sorry for the delay if that's what you meant.

In either way, are you using a logging package at the moment or what does your logging setup look like at the moment? I can show you how to do either thing with drift if you provide more details on how you're processing logs at the moment.

[madsane29]

Basically I created a "logs" table in the same database that I use for the app.

In this "logs" table I am writing all kind of logs. Where is the user in the app, did the user create a new object, did the API call happened etc.

So whenever I want to log, I just create a LogCompanion.insert(...), then I make a logDao.insertEntity() call.

Now if I could have these Drift: SELECT * ... and Drift: UPDATE table ... logs that I see in the console whenever I set the logStatement true, it would lower the amount of code I have to write to log the inserts/updates/selects what are happening during use of the app. Also could not happen that I miss a place where a DB interaction happens and I forgot to log it.

[simolus3]

So whenever I want to log, I just create a LogCompanion.insert(...), then I make a logDao.insertEntity() call.

Nice! Here's a problem though: If you want to log all SQL statements executed by drift and you execute an SQL query for each added log entry, you run into infinite recursion. So if you prefer to log all statements, you'd have to find a way that doesn't create log entries for insertions into your logs table.

Personally, I don't think it makes much sense to log every single database interaction in user apps as long as you log database errors. Still, you can do something like this in main or wherever you open your database:

void main() {
  final myDatabase = AppDatabase();
  driftRuntimeOptions.debugLog = (message) {
    debugPrint(message);
    //  todo: You'll want to be really really sure that this if is working as intended.
    if (!message.contains('INSERT INTO logs')) {
      myDatabase.log.insertOne(LogCompanion.insert(/* use message here */));
    }
  };
}

[madsane29]

Yeah, it might create a lot of log entities in my DB so might lower the volume somehow later. At the moment it will help me to find some strange bugs in my app.

This is exactly what I needed, thank you!