-
Notifications
You must be signed in to change notification settings - Fork 422
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dbName
with slash doesn't work
#2152
Comments
@lucasfcnunes I spent an afternoon trying to verify this issue, and try to change k3s.go but to no avail. Finally I noticed that the version of go-sql-driver used by k3s is v1.17, go.mod but the I tried to submit a pr to k3s to upgrade the go-sql-driver version, after which vcluster should be back to normal. |
dbname
with slash doesn't workdbName
with slash doesn't work
@mayooot, I noticed that operators in |
If those get fixed in k3s, let us know what version it's fixed in and then we can get the latest versions of k3s and kine and we can then update it. Have you tried using the default vanilla k8s version? Or is there a specific reason why you must run k3s? |
@lucasfcnunes seems like we only need to update kine now to make this work. I'll create a PR for this. |
@FabianKramm it's not completed on MySQL.
|
The next kine release should fix it for MySQL too. |
@deniseschannon |
What happened?
Trying to use as
dbName
in the DSN:vcluster/dev
vcluster%2Fdev
What did you expect to happen?
I expected to see Vcluster creating and using the database/schema with a slash in its name.
How can we reproduce it (as minimally and precisely as possible)?
docker run --rm -e MYSQL_ROOT_PASSWORD=root -p 3306:3306 mysql:8.0.33
--
PS: MySQL does support the following DDL:
Anything else we need to know?
schema/branch
.Host cluster Kubernetes version
vcluster version
VCluster Config
The text was updated successfully, but these errors were encountered: