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.
Hi, atlasgo devs,
I want to contribute the integration for RisingWave, a pgwire-compatible database primarily targeting streaming. We've heard from several users praising the usability of atlasgo, and we believe integrating both tools would streamline the user experience.
At first, I tried directly connecting RisingWave via the Postgres connector, but atlasgo threw serveral errors due to the lack of some SQL features at the RisingWave side. These features are currently unnecessary in RisingWave's context, so I had to tweak atlasgo to work properly with RisingWave.
A major modification is that I introduced a separate branch to check if atlas is connecting to RisingWave:
If it is, all further execution will go to RisingWave-specific implementation.
Another tricky part is:
I slightly adjusted the comparison, removing
::regclass::oid
. I usedtext
instead ofoid
for comparison. This is because RisingWave doesn't supportregclass
noroid
. I thin usingtext
would achieve better compatibility with other PG-like databases. 😄 I hope this modification would not break anything.