You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using mssql results in every key after the first key being detected as already existing.
It appears the check for "does this key exists" is actually running "does any key exist"
models/ssh_key.go line 360 is the line.
This is most likely caused by go-xorm. It appears as if it is ignoring the text condition for mssql.
A workaround is has, err := x.Where("content=?",content).Where("type=?",KeyTypeUser).Get(&PublicKey{})
...
The text was updated successfully, but these errors were encountered:
btrepp
changed the title
Every public key after the first added is a 'duplicate'
Every public key after the first added is a 'duplicate' for MSSQL
Jan 19, 2017
[x]
):Description
Using mssql results in every key after the first key being detected as already existing.
It appears the check for "does this key exists" is actually running "does any key exist"
models/ssh_key.go line 360
is the line.This is most likely caused by go-xorm. It appears as if it is ignoring the text condition for mssql.
A workaround is
has, err := x.Where("content=?",content).Where("type=?",KeyTypeUser).Get(&PublicKey{})
...
The text was updated successfully, but these errors were encountered: