New to bytebase. Error when getting database schema on sync schema
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 14.5k
- Forks
- 984
- Avg merge
- 15h 58m
- Merged PRs (30d)
- 256
Description
Provide the Bytebase version you are using
v2.16.0
Describe the bug
Hi. New to bytebase and new to this bugs submit. Please forgive me if i don't use it correctly.
I followed the tutorial adapting it to two databases i have. i have the free version of bytebase.
I tried to sync schemas for the first time and got this error:
/bytebase.v1.DatabaseService/GetDatabaseSchema INTERNAL: failed to get concise schema, error Syntax error at line 5757:120
related text: ASC, SYS_EXTRACT_UTC("END_DATE") ASC, ASC
It seems to be a part of an index related to a timestamp(6) column called end_date.
Is it a known issue? Am i doing something wrong?
Steps to reproduce
Create two databases with the bytebase user in oracle.
Those databases already have data in the same schemas (that are different from bytebase).
Have (i suppose) an index with a timestamp(6) column in it in one schema.
Try to sync schemas.
Expected behavior
When putting the source schema throws the error and don't let you click next.
Provide the database you are using
Oracle 19c
Provide the version control system 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
Reproduce schema synchronization with Oracle 19c using the reported Bytebase version and an index involving a timestamp(6) end_date column. Start with the reported parser error at line 5757:120 and its related index text. Done means the source schema is accepted and the sync flow can proceed without the syntax error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100