h3n4l

Hi @mencner, thanks for your contribution. I cannot reproduce this problem in Bytebase of version 1.1.0, here are my steps to reproduce it: 1. Run PostgreSQL 13.6 with docker 2....

Sorry, I can reproduce this problem in Bytebase of version 1.1.0 now. I use `CREATE UNIQUE INDEX "ix_fileimport_vault_balanceOpenItems_dwh_ouid" ON tbl(id);` (ix_fileimport_vault_balanceOpenItems_dwh_ouid with double quotes). @mencner

Thanks for your contributions @mencner. Feel free to reopen this issue if you have any questions. ^ ^ @mencner

Sorry for that. I'm guessing there might be a conflict with some fixes. I will try to fix it again in the next release. @mencner

> Are we sure, that this is not a different issue? Because the error message is different? I am not sure about this. Does your index name contain double quotes?...

BTW, can we remove the first empty line in each code block? It's meaningless. 

Hi @manideep-qlub, thanks for your feedback. > I want to know if its feasible that Bytebase updates the same existing issue if same file is updated in GIT with correct...

Any update for this one?

Thanks @keleus , we will look into this issue.

> The bytebase helm chart version is always 1.1.0. We have other versions before, likes 1.0.0, but we deletes these versions because we deprecated some Bytebase images. > When new...