pg_isok 0.4.2
- This Release
- pg_isok 0.4.2
- Date
- Status
- Testing
- Latest Unstable
- pg_isok 0.1.4 —
- Other Releases
- Abstract
- Query based data integrity management
- Description
- Isok can help you manage your data's integrity, especially when little technical effort can be spared, or manual review is involved, or data cleanup is done over time. It is especially suited when importing "dirty" data into PostgreSQL for cleanup, and for corner cases where business logic is "fuzzy". Isok can monitor anything that can be reported with an SQL query. Unlike simply running a query, which reports the _existence_ of questionable data patterns, Isok produces reports alerting you of _changes_ to questionable data patterns, so that only new problems need be reviewed. To use Isok you write SQL queries, which produce reports alerting you of questionable data patterns. Then, on a row by row basis, you can defer, possibly forever, the appearance of individual alerts on future reports. Isok's expected usage targets data integrity maintenance and data cleanup. Isok can be built as pure SQL, for installation in the cloud or other managed PostgreSQL instances. It targets PostgreSQL 10 or later.
- Released By
- kop
- License
- agpl_3
- Resources
- Special Files
- Tags
Extensions
- pg_isok 0.4.2
- Query based data integrity management
Documentation
- The-Main-Tables
- The Main Tables
- Acknowledgements-and-History
- H. Acknowledgments and History
- How-Isok-Works
- How Isok Works
- Mitigation-Strategies
- Mitigation Strategies
- Why-Use-Isok
- Why Use Isok?
- isok-The-Functions
- The Functions (Running Isok)
- Example-Periodic-Reporting-via-Email-Using-systemd
- Example Periodic Reporting via Email Using systemd
- The-SowkeDB-Acknowledgements
- The SokweDB Acknowledgments
- agpl
- J. GNU Affero General Public License version 3
- Introduction
- A Very Short Introduction
- appendix-Periodic-Execution
- E. Periodic Execution
- Isok-Overview
- An Overview of the Tables
- Some-Notes-on-Query-ID-Style
- B. Some Notes on Query ID Style
- index
- Isok -- Query Based Data Integrity Management For PostgreSQL
- FAQ
- C. Frequently Asked Questions
- extend-issue-classification
- Extend Issue Classification
- A-Start-To-Finish-Set-of-Examples
- A Start-To-Finish Set of Examples
- Local-Copies-of-the-Documentation
- D. Local Copies of the Documentation
- Limiting-Access
- Limiting Access
- isok-The-Support-Tables
- The Support Tables
- Roles
- Roles
- What-Queries-Access-Matters
- What Queries Access Matters
- The-Search-Path
- The Search Path
- cc0-Notice
- Notice
- Building-and-Distributing
- Building and Distributing
- Developing
- G. Developing
- pg_isok
- Query based data integrity management
- CC0-1.0-Universal-Deed
- K. CC0 1.0 Universal Deed
- isok
- Isok -- Query Based Data Integrity Management For PostgreSQL
- cc0-1.0-universal
- L. CC0 1.0 Universal
- The-Babase-Acknowledgements
- The Babase Acknowledgments
- Installation
- Installation
- cc0-Other-Information
- Other Information
- Licensing-Terms
- I. Licensing Terms -- Licensed Under The AGPL v3.0+ (Examples Excepted)
- Modify-Isoks-Generated-SQL
- Modify Isok's Generated SQL
- cc0-No-Copyright
- No Copyright
- Tool-Requirements
- Tool Requirements
- run_isok_queries
- run_isok_queries
- The-Gombe-Mother-Infant-Project-Acknowledgements
- The Gombe Mother-Infant Project Acknowledgments
- Fully-Utilize-ISOK_RESULTS.QR_Extra
- Fully Utilize ISOK_RESULTS.QR_Extra
- appendix-Security-Considerations
- A. Security Considerations
- Wrap-run_isok_queries
- Wrap run_isok_queries()
- appendix-Techniques-For-Making-Local-Extensions-to-Isok
- F. Techniques For Making Local Extensions to Isok
- Creating-an-Audit-Trail
- Creating an Audit Trail