Currently, there's no logging of errors or debugging information, leading to the need to insert println! everywhere when something goes wrong.
Add a logging framework and basic logging of important things (SQL generation at debug level, any errors that bubble up to holmes_exec!), with the intent that when debugging in the future, those lines will be added as logging commands rather than println!s to be removed.
Currently, there's no logging of errors or debugging information, leading to the need to insert
println!everywhere when something goes wrong.Add a logging framework and basic logging of important things (SQL generation at debug level, any errors that bubble up to
holmes_exec!), with the intent that when debugging in the future, those lines will be added as logging commands rather thanprintln!s to be removed.