feat: 添加分页功能和缓存管理,优化问答记录展示
This commit is contained in:
Vendored
+11
-16
@@ -1,27 +1,22 @@
|
||||
// server/api/cache/clear.post.ts - 清空答题缓存接口
|
||||
import { answerCache } from "~~/server/utils/cache";
|
||||
import { serverEnv } from "~~/server/utils/env";
|
||||
// server/api/cache/clear.post.ts - 清空当前用户 DB 缓存接口
|
||||
import { prisma } from "~~/server/utils/db";
|
||||
import { createApiLogger } from "~~/server/utils/logging";
|
||||
|
||||
/**
|
||||
* 清空内存缓存
|
||||
* 清缓存:将当前用户的 cacheClearedAt 更新为当前时间
|
||||
*
|
||||
* 这是一个管理类接口,必须携带有效 session cookie(由 api-auth middleware 统一鉴权)
|
||||
* 清理的是当前 Nuxt 进程内缓存;多实例部署时,每个实例都有自己的内存缓存
|
||||
* 之后查 DB 缓存时只命中该时间之后写入的记录,历史记录全部保留。
|
||||
* 必须携带有效 session cookie(由 api-auth middleware 统一鉴权)
|
||||
*/
|
||||
export default defineEventHandler((event) => {
|
||||
export default defineEventHandler(async (event) => {
|
||||
const logger = createApiLogger(event, "api.cache.clear");
|
||||
const userId = event.context.auth!.user.id;
|
||||
|
||||
// 缓存被关闭时不报错,只明确告诉调用方当前没有缓存可清
|
||||
if (!serverEnv.enableCache || !answerCache) {
|
||||
return {
|
||||
success: false,
|
||||
message: "缓存未启用"
|
||||
};
|
||||
}
|
||||
await prisma.user.update({
|
||||
where: { id: userId },
|
||||
data: { cacheClearedAt: new Date() }
|
||||
});
|
||||
|
||||
// 清空当前进程内缓存,DB 记录不受影响
|
||||
answerCache.clear();
|
||||
logger.info("finish_success");
|
||||
|
||||
return {
|
||||
|
||||
Reference in New Issue
Block a user