sangreal-db

基于sqlalchemy的python数据库orm包，加入对交互式编程的支持，更简易的API。

注意

自动补全功能在ipython>7.1.1的版本下会出现卡顿现象，如果需要，请回滚至该本版或以下。

安装

pip install sangreal-db

使用方法

建表

from sangreal_db import DataBase
from sqlalchemy import create_engine

engine = create_engine('mysql://....')
# or
engine = 'mysql://....'

# 实例化
db = DataBase(engine, schema=None)

from sqlalchemy import Column, Integer, String

# 构建User类
class User(db.Base):
    __tablename__ = 'users'
    id = Column(Integer, primary_key=True)
    name = Column(String(20))
    fullname = Column(String(20))
    password = Column(String(20))

    def __repr__(self):
        return "<User(name='%s', fullname='%s', password='%s')>" % (
            self.name, self.fullname, self.password)

# 建表
db.create_all()

查

更多api用法可参考python对Mysql操作和使用ORM框架（SQLAlchemy）

# database下以TABLE_NAME为表名的Table类
# TABLE_NAME为任意该database下存在主键的表
table = db.TABLE_NAME

# 表TABLE_NAME下以COLUMN为列名的Column类
table.COLUMN

# 继承了sqlalchemy的Query，支持同样方法
# 返回实例化对象序列
db.query(table).filter(table.COLUMN==....).all() 

# 返回DataFrame
db.query(table).filter(...).to_df()

增/改 (适用于逐条增改)

# 增
t_obj_add = table(c1=xxx, c2=xxx, c3=xxx)
db.update(t_obj_add)
db.commit()

# 改
t_obj_update = db.query(table).filter(...).all()
for t in t_obj_update:
    t.c1 = xxx
db.update(t_obj_update)
db.commit()

# 或者一起搞
# 构建一个iterable对象
t_change = [t_obj_add] + t_obj_update
db.update(t_change)
db.commit()

# 或者另外一种模式
db.query(table).filter(...).update({table.c1: "hello"}, synchronize_session=False)
db.commit()

批量插入

import pandas as pd
df = pd.DataFrame(...)
# 批量插入支持DataFrame格式 或 list of dicts [{'xx': ...}, ..., {}]
# ignore默认为True，如果存在唯一性索引，会忽略重复键错误
# 解决了pandas中 if_exist='append'中重复插入报错的问题
db.insert(table, df, ignore=True)
db.commit()

删

# 删
t_obj_delete = db.query(table).filter(...).first()
db.delete(t_obj_delete)
db.commit()

# 或者另外一种模式
db.query(table).filter(...).delete()
db.commit()

ipython or jupyter-notebook

实例化Database类后，sangreal-db会自动为该实例添加以表名命名的属性，这点在交互式编程中十分方便。

需要注意的是，该属性为懒加载，并不会一次性将database下的所有表映射成Table类，只有在单独调用时才会映射对应的表，解决了性能问题。

tables

columns

Metadata

Release files for sangreal-db 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sangreal-db 0.1.2
File	Size	Uploaded	Provenance
sangreal_db-0.1.2.tar.gz	29.8 kB	Nov 30, 2025	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for sangreal-db 0.1.2
File	Interpreter	ABI	Platform	Reset
sangreal_db-0.1.2-py3-none-any.whl 29.9 kB Nov 30, 2025 Without provenance	Python 3	none	any	Details

Total release size: 59.7 kB

Release files / sangreal_db-0.1.2.tar.gz

Download URL	sangreal_db-0.1.2.tar.gz
Size	29.8 kB
Tags	Source
SHA-256 checksum How to use checksums	`2c2c2c520c692372ec0b9b5a5927ddd45354cc934a8b3487b831914a23e086a3`
BLAKE2b-256 checksum How to use checksums	`90ffbcdafdfbdb89a41f57fa5512c69918ca06975f601eb2fb8d48703547a517`
Upload date	Nov 30, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/6.2.0 CPython/3.11.7`

Release files / sangreal_db-0.1.2-py3-none-any.whl

Download URL	sangreal_db-0.1.2-py3-none-any.whl
Size	29.9 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`2639b824e287005f295e229282b1f0818d0ab845d7295aa761e582df925e48d5`
BLAKE2b-256 checksum How to use checksums	`b79e1c3799b960a659f2ce063351e3d7d711e1488a6a604d13a2ac15f7fd98c2`
Upload date	Nov 30, 2025
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/6.2.0 CPython/3.11.7`

Security for sangreal-db 0.1.2

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.