Skip to content
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

Can't create new flags with pgsql #101

Closed
marceloboeira opened this issue Mar 9, 2018 · 2 comments · Fixed by #113
Closed

Can't create new flags with pgsql #101

marceloboeira opened this issue Mar 9, 2018 · 2 comments · Fixed by #113

Comments

@marceloboeira
Copy link
Member

Basically, I've started a pod on our cluster with sqlite, everything works well. However, when I switched to postgres nothing works anymore.

Steps to Reproduce (for bugs)

  1. Use a Postgres driver
  2. Start the pod
  3. Try to create a new flag
  4. See it fail

screen shot 2018-03-09 at 16 17 16

time="2018-03-09T15:11:14Z" level=info msg="/go/src/github.com/checkr/flagr/pkg/handler/eval_cache.go:89sql: Scan error on column index 6: Cannot scan {} into Attachment type"
time="2018-03-09T15:11:14Z" level=info msg="/go/src/github.com/checkr/flagr/pkg/handler/eval_cache.go:89sql: Scan error on column index 6: Cannot scan {} into Attachment type"
time="2018-03-09T15:11:14Z" level=info msg="/go/src/github.com/checkr/flagr/pkg/handler/eval_cache.go:89sql: Scan error on column index 6: Cannot scan {} into Attachment type"
time="2018-03-09T15:11:14Z" level=error msg="reload evaluation cache error" err="sql: Scan error on column index 6: Cannot scan {} into Attachment type; sql: Scan error on column index 6: Cannot scan {} into Attachment type; sql: Scan error on column index 6: Cannot scan {} into Attachment type; sql: Scan error on column index 6: Cannot scan {} into Attachment type"
time="2018-03-09T15:11:14Z" level=info msg="/go/src/github.com/checkr/flagr/pkg/handler/eval_cache.go:89sql: Scan error on column ind

Context

Trying to create a new flag with the Postgres driver

Your Environment

  • Version used (flagr version): latest
  • Operating System and version (uname -a): Linux **-846cbb9848-nd8vt 4.4.111-k8s #1 SMP Sun Jan 14 19:32:08 UTC 2018 x86_64 GNU/Linux
  • Link to your project: --
@marceloboeira
Copy link
Member Author

marceloboeira commented Mar 12, 2018

Update

I have switched the driver to mysql, with a mysql database of course, and now I don't experience that error. But still, if pgsql is supported the other issue should be fixed.

@zhouzhuojie
Copy link
Collaborator

Thanks for reporting, I will take a look and see how to fix it for pgsql. Currently, we are using MySQL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants