fix: use module logger instead of root logger in b_aiosqlite.py

[dashitongzhi]

Problem

In burr/integrations/persisters/b_aiosqlite.py, the logger is created using logging.getLogger() (no arguments), which returns the root logger. Every other persister module in the same package uses logging.getLogger(__name__) to create a properly scoped module logger.

Using the root logger causes log messages to bypass the module's namespace, making it harder to filter or configure logging for this specific module, and can lead to unexpected log output appearing in root logger handlers even when the module's logging is intended to be suppressed.

Fix

Changed logging.getLogger() to logging.getLogger(__name__) for consistency with all other persister implementations:

# Before
logger = logging.getLogger()

# After
logger = logging.getLogger(__name__)

This is a one-line fix. All other persisters already use this pattern:

• b_pymongo.py → logging.getLogger(__name__)
• b_mongodb.py → logging.getLogger(__name__)
• b_redis.py → logging.getLogger(__name__)
• b_asyncpg.py → logging.getLogger(__name__)
• b_psycopg2.py → logging.getLogger(__name__)
• postgresql.py → logging.getLogger(__name__)

[Copilot]

Pull request overview

Updates the SQLite async persister to use a module-scoped logger instead of the root logger, aligning its logging behavior with the rest of the persister integrations.

Changes:

• Switch b_aiosqlite.py from logging.getLogger() (root logger) to logging.getLogger(__name__) (module logger).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dashitongzhi]

Friendly ping for review 🙏 This is a small, focused fix. CI is passing. Thank you!

[dashitongzhi]

Hi! 👋 This PR has passed all CI checks and looks ready for review. Could a maintainer please take a look when they have a chance? Thank you!

[skrawcz]

LGTM — logging.getLogger() → logging.getLogger(__name__) for consistency with all other persister modules. One-line fix, correct pattern.