Skip to content

Conversation

@dimitri-yatsenko
Copy link
Member

@dimitri-yatsenko dimitri-yatsenko commented Jan 27, 2026

Summary

  • Front page: Update to indicate DataJoint 2.0–2.1 pre-release coverage
  • Settings rename: database.schema_prefixdatabase.database_prefix
  • Env var rename: DJ_SCHEMA_PREFIXDJ_DATABASE_PREFIX
  • Logging docs: Document JOBS log level and DJ_LOG_STREAM env var

Rationale

database_prefix rename

Renames database.schema_prefix to database.database_prefix to avoid confusion with the store's schema_prefix setting (used for schema-addressed storage paths).

  • In MySQL: schema = database
  • In PostgreSQL: projects use dedicated databases
  • database_prefix is technically accurate for both backends

Logging documentation

Adds documentation for PR #1352 logging changes:

  • JOBS log level (15) between DEBUG and INFO for job status visibility
  • DJ_LOG_STREAM env var for stdout/stderr routing (default: stdout)

Related

  • datajoint-python PR #1351 — Implements the database_prefix rename
  • datajoint-python PR #1352 — Implements the logging changes

Files Changed

  • src/index.md — Version banner update
  • src/reference/configuration.md — Settings table, logging section
  • src/how-to/deploy-production.md — database_prefix and logging updates
  • src/reference/specs/autopopulate.md — Job status logging section

🤖 Generated with Claude Code

- Front page: Update to indicate 2.0-2.1 pre-release coverage
- Rename database.schema_prefix to database.database_prefix
- Rename DJ_SCHEMA_PREFIX to DJ_DATABASE_PREFIX

This aligns with datajoint-python PR #1351 which renames the setting
to avoid confusion with store's schema_prefix (schema-addressed storage).

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@dimitri-yatsenko dimitri-yatsenko merged commit 3412840 into main Jan 27, 2026
1 check passed
@dimitri-yatsenko dimitri-yatsenko changed the title Update to database_prefix and 2.x version Update database_prefix, logging docs, and 2.x version Jan 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants