docs: 收紧QQBot验证数据查询约束
This commit is contained in:
parent
de9dd56bb6
commit
227e5c0899
@ -170,10 +170,10 @@ Before applying SQL, take a transaction-consistent backup of all six
|
|||||||
rolling back Admin and API while retaining events, deliveries, and send logs;
|
rolling back Admin and API while retaining events, deliveries, and send logs;
|
||||||
do not use `DROP TABLE` or history deletion as an application rollback.
|
do not use `DROP TABLE` or history deletion as an application rollback.
|
||||||
|
|
||||||
Verification output must contain only counts or ID/index summaries. Never query
|
Verification output must contain only counts or ID/index summaries. Never
|
||||||
or print `payload`, `rendered_message`, `target_id`, credentials, provider
|
select/project or print raw `payload`, `rendered_message`, `target_id`,
|
||||||
objects, or production values. The implementation and automated API evidence
|
credentials, provider objects, or production values. The implementation and
|
||||||
exist, but real local CRUD, browser pages, database-backed Outbox/DDNS flow,
|
automated API evidence exist, but real local CRUD, browser pages,
|
||||||
and authorized QQ delivery remain unverified because safe local prerequisites
|
database-backed Outbox/DDNS flow, and authorized QQ delivery remain unverified
|
||||||
are unavailable; this documentation change performed no push, deployment, or
|
because safe local prerequisites are unavailable; this documentation change
|
||||||
production SQL.
|
performed no push, deployment, or production SQL.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user