- 新增图像生成接口,支持试用、积分和自定义API Key模式 - 实现生成图片结果异步上传至MinIO存储,带重试机制 - 优化积分预扣除和异常退还逻辑,保障用户积分准确 - 添加获取生成历史记录接口,支持时间范围和分页 - 提供本地字典配置接口,支持模型、比例、提示模板和尺寸 - 实现图片批量上传接口,支持S3兼容对象存储 feat(admin): 增加管理员角色管理与权限分配接口 - 实现角色列表查询、角色创建、更新及删除功能 - 增加权限列表查询接口 - 实现用户角色分配接口,便于统一管理用户权限 - 增加系统字典增删查改接口,支持分类过滤和排序 - 权限控制全面覆盖管理接口,保证安全访问 feat(auth): 完善用户登录注册及权限相关接口与页面 - 实现手机号验证码发送及校验功能,保障注册安全 - 支持手机号注册、登录及退出接口,集成日志记录 - 增加修改密码功能,验证原密码后更新 - 提供动态导航菜单接口,基于权限展示不同菜单 - 实现管理界面路由及日志、角色、字典管理页面访问权限控制 - 添加系统日志查询接口,支持关键词和等级筛选 feat(app): 初始化Flask应用并配置蓝图与数据库 - 创建应用程序工厂,加载配置,初始化数据库和Redis客户端 - 注册认证、API及管理员蓝图,整合路由 - 根路由渲染主页模板 - 应用上下文中自动创建数据库表,保证运行环境准备完毕 feat(database): 提供数据库创建与迁移支持脚本 - 新增数据库创建脚本,支持自动检测是否已存在 - 添加数据库表初始化脚本,支持创建和删除所有表 - 实现RBAC权限初始化,包含基础权限和角色创建 - 新增字段手动修复脚本,添加用户API Key和积分字段 - 强制迁移脚本支持清理连接和修复表结构,初始化默认数据及角色分配 feat(config): 新增系统配置参数 - 配置数据库、Redis、Session和MinIO相关参数 - 添加AI接口地址及试用Key配置 - 集成阿里云短信服务配置及开发模式相关参数 feat(extensions): 初始化数据库、Redis和MinIO客户端 - 创建全局SQLAlchemy数据库实例和Redis客户端 - 配置基于boto3的MinIO兼容S3客户端 chore(logs): 添加示例系统日志文件 - 记录用户请求、验证码发送成功与失败的日志信息
130 lines
4.6 KiB
Python
130 lines
4.6 KiB
Python
# dialects/mssql/json.py
|
|
# Copyright (C) 2005-2025 the SQLAlchemy authors and contributors
|
|
# <see AUTHORS file>
|
|
#
|
|
# This module is part of SQLAlchemy and is released under
|
|
# the MIT License: https://www.opensource.org/licenses/mit-license.php
|
|
# mypy: ignore-errors
|
|
|
|
from ... import types as sqltypes
|
|
|
|
# technically, all the dialect-specific datatypes that don't have any special
|
|
# behaviors would be private with names like _MSJson. However, we haven't been
|
|
# doing this for mysql.JSON or sqlite.JSON which both have JSON / JSONIndexType
|
|
# / JSONPathType in their json.py files, so keep consistent with that
|
|
# sub-convention for now. A future change can update them all to be
|
|
# package-private at once.
|
|
|
|
|
|
class JSON(sqltypes.JSON):
|
|
"""MSSQL JSON type.
|
|
|
|
MSSQL supports JSON-formatted data as of SQL Server 2016.
|
|
|
|
The :class:`_mssql.JSON` datatype at the DDL level will represent the
|
|
datatype as ``NVARCHAR(max)``, but provides for JSON-level comparison
|
|
functions as well as Python coercion behavior.
|
|
|
|
:class:`_mssql.JSON` is used automatically whenever the base
|
|
:class:`_types.JSON` datatype is used against a SQL Server backend.
|
|
|
|
.. seealso::
|
|
|
|
:class:`_types.JSON` - main documentation for the generic
|
|
cross-platform JSON datatype.
|
|
|
|
The :class:`_mssql.JSON` type supports persistence of JSON values
|
|
as well as the core index operations provided by :class:`_types.JSON`
|
|
datatype, by adapting the operations to render the ``JSON_VALUE``
|
|
or ``JSON_QUERY`` functions at the database level.
|
|
|
|
The SQL Server :class:`_mssql.JSON` type necessarily makes use of the
|
|
``JSON_QUERY`` and ``JSON_VALUE`` functions when querying for elements
|
|
of a JSON object. These two functions have a major restriction in that
|
|
they are **mutually exclusive** based on the type of object to be returned.
|
|
The ``JSON_QUERY`` function **only** returns a JSON dictionary or list,
|
|
but not an individual string, numeric, or boolean element; the
|
|
``JSON_VALUE`` function **only** returns an individual string, numeric,
|
|
or boolean element. **both functions either return NULL or raise
|
|
an error if they are not used against the correct expected value**.
|
|
|
|
To handle this awkward requirement, indexed access rules are as follows:
|
|
|
|
1. When extracting a sub element from a JSON that is itself a JSON
|
|
dictionary or list, the :meth:`_types.JSON.Comparator.as_json` accessor
|
|
should be used::
|
|
|
|
stmt = select(data_table.c.data["some key"].as_json()).where(
|
|
data_table.c.data["some key"].as_json() == {"sub": "structure"}
|
|
)
|
|
|
|
2. When extracting a sub element from a JSON that is a plain boolean,
|
|
string, integer, or float, use the appropriate method among
|
|
:meth:`_types.JSON.Comparator.as_boolean`,
|
|
:meth:`_types.JSON.Comparator.as_string`,
|
|
:meth:`_types.JSON.Comparator.as_integer`,
|
|
:meth:`_types.JSON.Comparator.as_float`::
|
|
|
|
stmt = select(data_table.c.data["some key"].as_string()).where(
|
|
data_table.c.data["some key"].as_string() == "some string"
|
|
)
|
|
|
|
.. versionadded:: 1.4
|
|
|
|
|
|
"""
|
|
|
|
# note there was a result processor here that was looking for "number",
|
|
# but none of the tests seem to exercise it.
|
|
|
|
|
|
# Note: these objects currently match exactly those of MySQL, however since
|
|
# these are not generalizable to all JSON implementations, remain separately
|
|
# implemented for each dialect.
|
|
class _FormatTypeMixin:
|
|
def _format_value(self, value):
|
|
raise NotImplementedError()
|
|
|
|
def bind_processor(self, dialect):
|
|
super_proc = self.string_bind_processor(dialect)
|
|
|
|
def process(value):
|
|
value = self._format_value(value)
|
|
if super_proc:
|
|
value = super_proc(value)
|
|
return value
|
|
|
|
return process
|
|
|
|
def literal_processor(self, dialect):
|
|
super_proc = self.string_literal_processor(dialect)
|
|
|
|
def process(value):
|
|
value = self._format_value(value)
|
|
if super_proc:
|
|
value = super_proc(value)
|
|
return value
|
|
|
|
return process
|
|
|
|
|
|
class JSONIndexType(_FormatTypeMixin, sqltypes.JSON.JSONIndexType):
|
|
def _format_value(self, value):
|
|
if isinstance(value, int):
|
|
value = "$[%s]" % value
|
|
else:
|
|
value = '$."%s"' % value
|
|
return value
|
|
|
|
|
|
class JSONPathType(_FormatTypeMixin, sqltypes.JSON.JSONPathType):
|
|
def _format_value(self, value):
|
|
return "$%s" % (
|
|
"".join(
|
|
[
|
|
"[%s]" % elem if isinstance(elem, int) else '."%s"' % elem
|
|
for elem in value
|
|
]
|
|
)
|
|
)
|