bigserial MAXVALUE convert error when sync schema
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 14.5k
- Forks
- 983
- Avg merge
- 15h 58m
- Merged PRs (30d)
- 256
Description
Provide the Bytebase version you are using
v3.7.0
Describe the bug
should have no difference about bigserial MAXVALUE between two table
Steps to reproduce
- given a database table with bigserial id field, go sync schema
- select source database and target database
- show MAXVALUE difference
Expected behavior
should have no difference with MAXVALUE
Provide the database you are using
No response
Additional context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the sync schema flow described in the reproduction steps, using a PostgreSQL table with a bigserial id field and comparing source and target databases. Confirm where the MAXVALUE difference is reported; done when equivalent bigserial sequences no longer produce a schema difference. No source file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100