feat: Add backward-compatible fetch() with deprecation warning#1355
Merged
dimitri-yatsenko merged 2 commits intomasterfrom Jan 28, 2026
Merged
feat: Add backward-compatible fetch() with deprecation warning#1355dimitri-yatsenko merged 2 commits intomasterfrom
dimitri-yatsenko merged 2 commits intomasterfrom
Conversation
github-actions
bot
added
enhancement
dimitri-yatsenko
force-pushed
the
feat/fetch-backward-compat
branch
4 times, most recently
from
de65813 to
d7e477f
Compare
Restore fetch() method for easier migration from DataJoint 0.14.
The method emits a DeprecationWarning and maps to 2.0 methods:
- fetch() → to_arrays()
- fetch(as_dict=True) → to_dicts()
- fetch('col1', 'col2') → proj(...).to_dicts()
- fetch('col1', 'col2', as_dict=False) → to_arrays('col1', 'col2')
- fetch(format='frame') → to_pandas()
Supports order_by, limit, offset, squeeze parameters.
Updates migration guide link to new location.
Bump version to 2.0.0a27.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
dimitri-yatsenko
force-pushed
the
feat/fetch-backward-compat
branch
from
d7e477f to
c9c6c5b
Compare
dimitri-yatsenko
changed the title
esutlie
approved these changes
Jan 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Restores the
fetch()method for easier migration from DataJoint 0.14. Emits a deprecation warning and delegates to 2.0 output methods.Motivation
Production pipelines have 100+
fetch()calls deeply integrated with downstream logic. Requiring immediate rewrites creates migration barriers and version lock-in risk.This allows gradual migration: code works immediately on 2.0, deprecation warnings guide incremental updates.
Changes
1. Backward-compatible
fetch()Emits
DeprecationWarningand maps to 2.0 methods:fetch()to_arrays()fetch(as_dict=True)to_dicts()fetch('col1', 'col2')proj('col1', 'col2').to_dicts()fetch('col1', 'col2', as_dict=False)to_arrays('col1', 'col2')fetch(format='frame')to_pandas()Supports
order_by,limit,offset, andsqueezeparameters.2. Unit tests
Added 9 unit tests covering all fetch() patterns and parameter passthrough.
3. Fix migration guide link
Updated
migrate-from-0x→migrate-to-v204. Version bump
2.0.0a26 → 2.0.0a27
Testing
All unit tests pass.
Related
🤖 Generated with Claude Code