Closed EinKrebs closed 2 years ago
That does not make sense to me. The the common use case is to create tables in the database where you are connecting. Users could also specify the same database for both.
@pavolloffay So, is the current approach in PR okay?
No we cannot use script that uses USE
because of https://github.com/go-sql-driver/mysql/issues/173#issuecomment-28539448.
We can make a requirement for user to create a database before starting jaeger, however we need to change the db name in scripts as I mentioned before.
No we cannot use script that uses
USE
because of go-sql-driver/mysql#173 (comment).We can make a requirement for user to create a database before starting jaeger, however we need to change the db name in scripts as I mentioned before.
@pavolloffay Then maybe we should keep "default" as the default database name. In that case we could get rid of our complex two-step connection.
Can you explain why? I think it's still useful for quick demos as default.
Can you explain why? I think it's still useful for quick demos as default.
What to explain?
Why the default database cannot be used :)
It sure can, and I want it to be used. But from your guide to sharding and replication I thought that we should create tables in jaeger database. Now I see you're okey with using default as the default database name. Gonna change it in PR.
@pavolloffay All done, I guess.
Did you test this with a real CH server?
Also note that it should work for any database name that is in the config.
Did you test this with a real CH server?
Yes, I did, with custom database names as well as custom table names.
Great work @EinKrebs
Great work @EinKrebs
Thanks a lot.
@pavolloffay maybe we should use 2 config options:
This will make things much easier.