2 Repos
Awesome GitHub RepositoriesSQL Query Persistence
Mechanisms for storing SQL statements and their associated execution configurations for later reuse.
Distinct from SQL Query Execution: Candidates focus on the act of execution [f1_mt3] or debugging [f1_mt4], but not the persistence of the query documents themselves.
Explore 2 awesome GitHub repositories matching data & databases · SQL Query Persistence. Refine with filters or upvote what's useful.
Awesome SQL Query Persistence GitHub Repositories
Finde die besten Repos mit KI.Wir suchen mit KI nach den am besten passenden Repositories.
- sqlpad/sqlpad
sqlpad/sqlpad
5,186Auf GitHub ansehenSqlpad is a web-based SQL client and multi-tenant workbench used for writing, executing, and saving queries across multiple relational and analytical databases. It functions as an ODBC database manager that enables users to manage database connections and explore schemas through a browser interface. The platform distinguishes itself as a collaborative environment where users can share SQL documents and coordinate data analysis. It integrates identity federation via OpenID Connect, SAML, LDAP, and OAuth, and provides a visualization system that renders query results into charts and tables. Th
Enables the saving and persistence of SQL statements along with connection details and chart configurations.
JavaScript - tableplus/tableplus
TablePlus/TablePlus
3,799Auf GitHub ansehenTablePlus is a SQL database management GUI and professional administration tool designed for managing relational and NoSQL databases. It functions as a native SQL query client and relational data browser, providing a graphical interface for database administration, schema management, and data exploration. The project distinguishes itself through a staged-change commit system that buffers GUI-driven modifications locally for review before they are applied to the server. It also features a native-protocol connection layer for low-latency communication and secure connectivity via SSH tunneling.
Automatically persists unsaved query changes to prevent data loss when switching contexts.
