Trigger after SELECT

[Danny Holstein]

I understand a "trigger after SELECT" isn't a feature, I propose adding it to the feature request queue. I'm sure I can write a workaround, but I see good reasons to build it in as a feature.

- My specific need is for dumb label printer software with ODBC interface connection to MySQL, I want to access a view of label data that have not yet been printed and record details related to that access. In my case, specifically so that we may print once, and only once.

- For controlled information, including secret information, this feature would allow us to more simply log access to it. Using a combination of triggers, it'd be a simple task to see if we the access to the DB were abnormal.