Skip to content

Trivadis/plsql-and-sql-coding-guidelines

View on GitHub ↗Related repositories →

Trivadis PL/SQL & SQL Coding Guidelines

active 2023-08-162026-03-22 (UTC)

Partial coverage21,590 / 26,308 hourly files (82%) · 2 absent upstream · 4,717 failed, retryable2023-08-152026-08-15 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
150
Pushes
61
Pull requests
4
Issues
26
Stars
28
Forks
15

Activity over time

Daily event counts in the loaded window

Line chart, 950 days from 2023-08-16 to 2026-03-22. Pushes: 61 total, peak 24 in a day. Pull requests: 4 total, peak 2 in a day. Issues: 26 total, peak 13 in a day. Comments: 7 total, peak 3 in a day. Stars: 28 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
PhilippSalvisberg936144
sonarcloud[bot]3003
zrh5351000
MrUrdam1000

Recent activity

Latest issues, pull requests and releases

  • Issue comment#220PhilippSalvisberg2024-09-04 22:12
    G-1050 should not apply to check constraints
  • Issue#219MrUrdam2024-06-29 07:58
    Plans to introduce similar guidelines for Postgres PL/pgSQL
  • Issue#212PhilippSalvisberg2024-01-03 08:07
    New rule: Avoid autonomous transactions
  • Issue#211PhilippSalvisberg2023-10-27 09:20
    G-8310 value_error good_example
  • Issue comment#211PhilippSalvisberg2023-10-27 09:19
    G-8310 value_error good_example
  • Issue#210PhilippSalvisberg2023-09-29 14:58
    Highlight the lines that violate a guideline in the bad examples (and the fixed lines in the good examples)
  • Issue#209PhilippSalvisberg2023-09-29 13:33
    Fix revision history in about page
  • Issue#208PhilippSalvisberg2023-09-29 13:26
    Include column alias in G-3182
  • ReleasePhilippSalvisberg2023-09-27 16:00
    Trivadis PL/SQL & SQL Coding Guidelines v4.3
  • Issue#206PhilippSalvisberg2023-09-26 07:09
    Simplify G-1050 and related examples
  • Issue#203zrh5352023-09-14 11:59
    The tools do not work from a Windows host with git-bash
  • Issue#202PhilippSalvisberg2023-09-13 12:20
    New rule: Always specify column names instead of expressions in GROUP BY clauses.
  • Issue#197PhilippSalvisberg2023-09-13 11:55
    New rule: Always specify column aliases instead of positional references in GROUP BY clauses.
  • Issue#202PhilippSalvisberg2023-09-13 11:20
    New rule: Always specify column names instead of expressions in GROUP BY clauses.
  • Issue#200PhilippSalvisberg2023-09-08 16:10
    Fix catagorization of guideline severties.
  • Pull request#201PhilippSalvisberg2023-09-08 16:10
  • Issue comment#201sonarcloud[bot]2023-09-08 15:56
    Rework severity catagorization
  • Issue comment#201sonarcloud[bot]2023-09-08 15:33
    Rework severity catagorization
  • Pull request#201PhilippSalvisberg2023-09-08 15:32
  • Issue#200PhilippSalvisberg2023-09-06 12:33
    Fix catagorization of guideline severties.
  • Issue comment#194PhilippSalvisberg2023-09-01 11:02
    Various guidelines: eliminate violations (2-4 issues per guideline)
  • Issue#194PhilippSalvisberg2023-09-01 11:02
    Various guidelines: eliminate violations (2-4 issues per guideline)
  • Issue#189PhilippSalvisberg2023-09-01 11:01
    G-9030: eliminate violations
  • Issue comment#189PhilippSalvisberg2023-09-01 11:01
    G-9030: eliminate violations
  • Issue#191PhilippSalvisberg2023-09-01 10:59
    G-7110: eliminate violations

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 28 stars here means stars gained during the window, not the repo's star count.