mirror of
http://github.com/valkey-io/valkey
synced 2024-11-22 18:54:58 +00:00
LCS: allow KEYS / STRINGS to be anywhere.
Initially they needed to be at the end so that we could extend to N strings in the future, but after further consideration I no longer believe it's worth it.
This commit is contained in:
parent
0b16f8d444
commit
c89e1f2937
@ -510,9 +510,6 @@ void lcsCommand(client *c) {
|
||||
if (a != NULL) {
|
||||
addReplyError(c,"Either use STRINGS or KEYS");
|
||||
return;
|
||||
} else if (moreargs != 2) {
|
||||
addReplyError(c,"LCS requires exactly two strings");
|
||||
return;
|
||||
}
|
||||
a = c->argv[j+1]->ptr;
|
||||
b = c->argv[j+2]->ptr;
|
||||
@ -521,9 +518,6 @@ void lcsCommand(client *c) {
|
||||
if (a != NULL) {
|
||||
addReplyError(c,"Either use STRINGS or KEYS");
|
||||
return;
|
||||
} else if (moreargs != 2) {
|
||||
addReplyError(c,"LCS requires exactly two keys");
|
||||
return;
|
||||
}
|
||||
obja = lookupKeyRead(c->db,c->argv[j+1]);
|
||||
objb = lookupKeyRead(c->db,c->argv[j+2]);
|
||||
|
Loading…
Reference in New Issue
Block a user