View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001724 | Anope Stable (2.0.x series) | General | public | 2019-07-22 23:01 | 2019-07-24 08:33 |
Reporter | simos | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Summary | 0001724: NS SET KILL doesn't update fields on mysql table | ||||
Description | Running /NS SET KILL have some problem updating data on mysql. NS SET KILL on work fine and set 1 on KILLPROTECT sql field NS SET KILL quick work fine and set 1 on KILL_QUICK sql field NS SET KILL immed work fine and set 1 on KILL_IMMED sql field everything look work fine until you have set KILL QUICK or KILL IMMED , than sql data are no more correctly updated, ns set kill off, ns set kill immed and ns set kill quick set right value for your account but not on mysql table, this until you run NS SET KILL ON again wich update mysql table settings KILLPROTECT to 1 and NULL on the other. Not tested on mysq live. | ||||
Steps To Reproduce | trying the steps in description. | ||||
Tags | No tags attached. | ||||
|
I can reproduce this using m_sqlite and both db_sql and db_sql_live. In exact order: NS SET KILL on: updates the DB NS SET KILL quick: updates the DB NS SET KILL immed: does not update the DB NS SET KILL off: does not update the DB NS SET KILL on: updates the DB NS SET KILL off: updates the DB It seems like "on" helps reset the issue and the next command works, but then they stop working. |
|
I've set debug on and look for query, it seems that anope don't execute query if immed or quick is set until you run again ns set kill on . |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-07-22 23:01 | simos | New Issue | |
2019-07-24 00:54 | simos | Note Added: 0006856 | |
2019-07-24 08:33 | genius3000 | Note Added: 0006857 |