table: silent write drops and conflict-column binding - #7
Open
mzxchandra wants to merge 1 commit into
Open
Conversation
| created by the same command gets a different id in each workspace - bind the conflict column by | ||
| its literal name in the manual field, not through the id-holding selector. This is the opposite | ||
| of table binding, where the selector is the portable side. | ||
| - Design around the platform limits: tables cap at 10000 rows and queries at 1000 rows per page, |
Collaborator
There was a problem hiding this comment.
idk if we should hardcode this cap, this is dependent on their plan + we should have flexibility to change this in the future. Maybe just say that tables have maximum row limits, design with that in mind?
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.
Documents write semantics that fail silently: a row write drops any key the column schema does not define while reporting success, and column ids are workspace-local, so a conflict column must be bound by name to survive cross-workspace promotion. Also records the row and query limits worth designing around.
🤖 Generated with Claude Code
https://claude.ai/code/session_01MYsyypbYR5eT4rxM2vaeEF