[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-70775":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":17,"compositeScore":19,"rankGlobal":9,"rankLanguage":9,"license":20,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":23,"hasPages":21,"topics":24,"createdAt":9,"pushedAt":9,"updatedAt":27,"readmeContent":28,"aiSummary":29,"trendingCount":15,"starSnapshotCount":15,"syncStatus":30,"lastSyncTime":31,"discoverSource":32},70775,"sqlalchemy","sqlalchemy\u002Fsqlalchemy","The Database Toolkit for Python","https:\u002F\u002Fwww.sqlalchemy.org",null,"Python",11902,1696,109,185,0,10,30,62,110.89,"MIT License",false,"main",true,[25,26,5],"python","sql","2026-06-12 04:00:57","SQLAlchemy\n==========\n\n|PyPI| |Python| |Downloads|\n\n.. |PyPI| image:: https:\u002F\u002Fimg.shields.io\u002Fpypi\u002Fv\u002Fsqlalchemy\n    :target: https:\u002F\u002Fpypi.org\u002Fproject\u002Fsqlalchemy\n    :alt: PyPI\n\n.. |Python| image:: https:\u002F\u002Fimg.shields.io\u002Fpypi\u002Fpyversions\u002Fsqlalchemy\n    :target: https:\u002F\u002Fpypi.org\u002Fproject\u002Fsqlalchemy\n    :alt: PyPI - Python Version\n\n.. |Downloads| image:: https:\u002F\u002Fstatic.pepy.tech\u002Fbadge\u002Fsqlalchemy\u002Fmonth\n    :target: https:\u002F\u002Fpepy.tech\u002Fproject\u002Fsqlalchemy\n    :alt: PyPI - Downloads\n\n\nThe Python SQL Toolkit and Object Relational Mapper\n\nIntroduction\n-------------\n\nSQLAlchemy is the Python SQL toolkit and Object Relational Mapper\nthat gives application developers the full power and\nflexibility of SQL. SQLAlchemy provides a full suite\nof well known enterprise-level persistence patterns,\ndesigned for efficient and high-performing database\naccess, adapted into a simple and Pythonic domain\nlanguage.\n\nMajor SQLAlchemy features include:\n\n* An industrial strength ORM, built\n  from the core on the identity map, unit of work,\n  and data mapper patterns.   These patterns\n  allow transparent persistence of objects\n  using a declarative configuration system.\n  Domain models\n  can be constructed and manipulated naturally,\n  and changes are synchronized with the\n  current transaction automatically.\n* A relationally-oriented query system, exposing\n  the full range of SQL's capabilities\n  explicitly, including joins, subqueries,\n  correlation, and most everything else,\n  in terms of the object model.\n  Writing queries with the ORM uses the same\n  techniques of relational composition you use\n  when writing SQL.  While you can drop into\n  literal SQL at any time, it's virtually never\n  needed.\n* A comprehensive and flexible system\n  of eager loading for related collections and objects.\n  Collections are cached within a session,\n  and can be loaded on individual access, all\n  at once using joins, or by query per collection\n  across the full result set.\n* A Core SQL construction system and DBAPI\n  interaction layer.  The SQLAlchemy Core is\n  separate from the ORM and is a full database\n  abstraction layer in its own right, and includes\n  an extensible Python-based SQL expression\n  language, schema metadata, connection pooling,\n  type coercion, and custom types.\n* All primary and foreign key constraints are\n  assumed to be composite and natural.  Surrogate\n  integer primary keys are of course still the\n  norm, but SQLAlchemy never assumes or hardcodes\n  to this model.\n* Database introspection and generation.  Database\n  schemas can be \"reflected\" in one step into\n  Python structures representing database metadata;\n  those same structures can then generate\n  CREATE statements right back out - all within\n  the Core, independent of the ORM.\n\nSQLAlchemy's philosophy:\n\n* SQL databases behave less and less like object\n  collections the more size and performance start to\n  matter; object collections behave less and less like\n  tables and rows the more abstraction starts to matter.\n  SQLAlchemy aims to accommodate both of these\n  principles.\n* An ORM doesn't need to hide the \"R\".   A relational\n  database provides rich, set-based functionality\n  that should be fully exposed.   SQLAlchemy's\n  ORM provides an open-ended set of patterns\n  that allow a developer to construct a custom\n  mediation layer between a domain model and\n  a relational schema, turning the so-called\n  \"object relational impedance\" issue into\n  a distant memory.\n* The developer, in all cases, makes all decisions\n  regarding the design, structure, and naming conventions\n  of both the object model as well as the relational\n  schema.   SQLAlchemy only provides the means\n  to automate the execution of these decisions.\n* With SQLAlchemy, there's no such thing as\n  \"the ORM generated a bad query\" - you\n  retain full control over the structure of\n  queries, including how joins are organized,\n  how subqueries and correlation is used, what\n  columns are requested.  Everything SQLAlchemy\n  does is ultimately the result of a developer-initiated \n  decision.\n* Don't use an ORM if the problem doesn't need one.\n  SQLAlchemy consists of a Core and separate ORM\n  component.   The Core offers a full SQL expression\n  language that allows Pythonic construction\n  of SQL constructs that render directly to SQL\n  strings for a target database, returning\n  result sets that are essentially enhanced DBAPI\n  cursors.\n* Transactions should be the norm.  With SQLAlchemy's\n  ORM, nothing goes to permanent storage until\n  commit() is called.  SQLAlchemy encourages applications\n  to create a consistent means of delineating\n  the start and end of a series of operations.\n* Never render a literal value in a SQL statement.\n  Bound parameters are used to the greatest degree\n  possible, allowing query optimizers to cache\n  query plans effectively and making SQL injection\n  attacks a non-issue.\n\nDocumentation\n-------------\n\nLatest documentation is at:\n\nhttps:\u002F\u002Fwww.sqlalchemy.org\u002Fdocs\u002F\n\nInstallation \u002F Requirements\n---------------------------\n\nFull documentation for installation is at\n`Installation \u003Chttps:\u002F\u002Fwww.sqlalchemy.org\u002Fdocs\u002Fintro.html#installation>`_.\n\nGetting Help \u002F Development \u002F Bug reporting\n------------------------------------------\n\nPlease refer to the `SQLAlchemy Community Guide \u003Chttps:\u002F\u002Fwww.sqlalchemy.org\u002Fsupport.html>`_.\n\nCode of Conduct\n---------------\n\nAbove all, SQLAlchemy places great emphasis on polite, thoughtful, and\nconstructive communication between users and developers.\nPlease see our current Code of Conduct at\n`Code of Conduct \u003Chttps:\u002F\u002Fwww.sqlalchemy.org\u002Fcodeofconduct.html>`_.\n\nLicense\n-------\n\nSQLAlchemy is distributed under the `MIT license\n\u003Chttps:\u002F\u002Fwww.opensource.org\u002Flicenses\u002Fmit-license.php>`_.\n\n","SQLAlchemy 是一个用于 Python 的 SQL 工具包和对象关系映射器，旨在为应用程序开发者提供全面且灵活的 SQL 功能。其核心功能包括强大的 ORM 系统，支持声明式配置、自动事务同步等特性；关系导向的查询系统，能够透明地使用 SQL 的所有能力进行操作；以及灵活的预加载机制，有效管理相关集合与对象的缓存。此外，它还提供了独立于 ORM 的 Core 模块，用于更底层的数据库抽象与交互。适用于需要高效、高性能数据库访问，并且希望在 Python 代码中以自然方式处理复杂数据模型的应用场景。",2,"2026-06-11 03:34:07","high_star"]