So, aggregates, partitioning, metrics and referential sets, play us another tune...
Ten features of Schoenberg's mature twelve-tone practice are characteristic, interdependent, and interactive[1]:
1. Hexachordal inversional combinatoriality
2. Aggregates
3. Linear set presentation
4. Partitioning
5. Isomorphic partitioning
6. Invariants
7. Hexachordal levels
8. Harmony, "consistent with and derived from the properties of the referential set"
9. Metre, established through "pitch-relational characteristics"
10. Multidimensional set presentations
Tuesday, June 24, 2008
Why Schoenberg Rocks...
Personally, I have had a taste for the music of Arnold Schoenberg for a long time.
But now, I the wikipedia explains why:
Monday, June 02, 2008
MySQL 5.1: Measuring #queries/sec. using information_schema.GLOBAL_STATUS
MySQL 5.1 offers new
(This snippet is maintained on MySQL Forge)
This query could have been solved in a number of other ways involving subqueries, for example like this:
For now I'm sticking to my original snippet. The disadvantage to this approach is that it requires a hack to force aggregation of all rows from
The disadvantage of a using subqueries is that it would be slighly more verbose, and it would also require more scanning of
What do you think?
information
tables such as GLOBAL_STATUS
. This can be used to report certain performance metrics, such as the number of queries processed per second:
SELECT MAX( -- use MAX to force aggregation
IF(variable_name='Questions' -- no. of queries sent to server
, CAST(variable_value AS unsigned) -- make integer value
, 0 -- ignore if not 'Questions'
)
)
/ -- divide by
MAX( -- use MAX to force aggregation
IF(variable_name='Uptime' -- no. of seconds the server is up
, CAST(variable_value AS unsigned) -- make integer value
, 0 -- ignore if not 'Uptime'
)
) AS queries_per_second
FROM information_schema.GLOBAL_STATUS
WHERE variable_name in ('Questions', 'Uptime');
(This snippet is maintained on MySQL Forge)
This query could have been solved in a number of other ways involving subqueries, for example like this:
SELECT (SELECT CAST(variable_value AS unsigned)
FROM information_schema.GLOBAL_STATUS
WHERE variable_name = 'Questions')
/ (SELECT CAST(variable_value AS unsigned)
FROM information_schema.GLOBAL_STATUS
WHERE variable_name = 'Uptime') as queries_per_second
For now I'm sticking to my original snippet. The disadvantage to this approach is that it requires a hack to force aggregation of all rows from
GLOBAL_STATUS
to one single row (using MAX
), as well as some conditional expressions. The disadvantage of a using subqueries is that it would be slighly more verbose, and it would also require more scanning of
information_schema.GLOBAL_STATUS
, although I am unsure if that would really matter that much.What do you think?
Subscribe to:
Posts (Atom)
Year-to-Date on Synapse Analytics 5: Using Window Functions
For one of our Just-BI customers we implemented a Year-to-Date calculation in a Azure Synapse Backend. We encountered a couple of approache...
-
Like all procedural database languages I know, the MySQL stored procedure language supports explicit cursors . I just wrote "explicit c...
-
To whom it may concern, this is a quick note to bring the xmondrian project to your attention. Introduction: Open Source OLAP, Mondrian,...
-
Just the previous week, Anders mentioned the sql_mode with regard to Joomla . Past week, Shlomi 's started a nice discussion pertaini...