EDGAR Gallery

The EDGAR database contains detailed financial filings from U.S. public companies. The demo includes the most recent (2008) filing information from 1,000 public companies, including executive compensation data (courtesy of directEDGAR) and company facts and financials (from EDGAR Online). Perform your own financial analysis to see how executive salaries stack up against company performance.

EDGAR Dashboard

The Executive Compensation dashboard shows the power of HTRAF to create an interactive application by combining HTSQL queries with HTRAF elements like selectors and text inputs. See how easy it is to find the top earners by industry, name and title.

EDGAR Schema

EDGAR Queries

Try these queries to see what compensation packages executives at 1000 U.S. companies enjoy.

Return a table

◥/officer

Here’s the simplest possible HTSQL query — return all rows and columns from the officer table. As with all HTSQL queries, the URL is the query.

Select specific columns

◥/officer{officer_name, title}

Here’s another simple query that shows selection of two specific columns, officer_name and officer_title, from the officer table.

Add a simple filter

◥/officer{officer_name, title}
        ?title~'chief technology officer'

Same selector as the previous query, but here we’ve added a filter. This filter finds rows in the officer table where the title contains chief technology officer.

Add a simple link

◥/compensation{officer.officer_name, amount}

This illustrates a simple link. The base table is compensation. The first expression in the selector, officer.officer_name instructs HTSQL to return the officer_name column from the (related) officer table. Note that we don’t have to specify the join in any more detail because HTSQL already knows how the officer table is related to the compensation table.

Aggregate data

◥/company{name, count(officer)-, max(officer.sum(compensation.amount))}

This example shows an expression that is straightforward and reasonably intuitive in HTSQL — for each company, we return the number of officers and maximum total compensation given to those officers. Interestingly, the SQL equivalent is neither intuitive nor simple (go ahead, try it.) This is not an accident. We’ve spent the last six years working to make sure that HTSQL syntax is intuitive enough for business analysts and power users to understand, yet powerful enough for developers to use.