<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Logon Trigger on FromDual GmbH</title><link>https://www.fromdual.com/tags/logon-trigger/</link><description>Recent content in Logon Trigger on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Fri, 19 Jan 2024 17:19:42 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/logon-trigger/index.xml" rel="self" type="application/rss+xml"/><item><title>Enable General Query Log per Connection in MariaDB</title><link>https://www.fromdual.com/blog/enable-gerneral-quey-log-per-connection-in-mariadb/</link><pubDate>Wed, 10 Jul 2019 20:27:58 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/enable-gerneral-quey-log-per-connection-in-mariadb/</guid><description>&lt;p&gt;The &lt;a href="https://mariadb.com/kb/en/library/general-query-log/" target="_Blank" title="General Query Log"&gt;General Query Log&lt;/a&gt; in MariaDB is a Log (file or table) that logs every statement sent from the Application to the MariaDB Database Server from the Connect Command to the Quit Command. A simple example you can find here:&lt;/p&gt;</description></item><item><title>Last login of MySQL database users</title><link>https://www.fromdual.com/blog/last-login-off-mysql-database-users/</link><pubDate>Sat, 01 Dec 2012 10:05:50 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/last-login-off-mysql-database-users/</guid><description>&lt;p&gt;MySQL hosting providers can easily loose the overview over their customers and which user or schema is still in use and which not.&lt;/p&gt;</description></item><item><title>MySQL logon and logoff trigger for auditing</title><link>https://www.fromdual.com/blog/mysql-logon-and-logoff-trigger-for-auditing/</link><pubDate>Fri, 10 Dec 2010 23:23:51 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/mysql-logon-and-logoff-trigger-for-auditing/</guid><description>&lt;p&gt;&lt;a href="https://www.fromdual.com/mysql-logon-trigger"&gt;A while ago&lt;/a&gt; I did some research about MySQL audit functionality and logon a and logoff triggers. MySQL and MariaDB provide a logon trigger in the form of the init_connect variable but no logoff trigger where most of the work for auditing would be done. When we would have a logoff trigger we could track the login and possibility some activity of a user and implement auditing functionality.&lt;/p&gt;</description></item><item><title>MySQL logon trigger</title><link>https://www.fromdual.com/blog/mysql-logon-trigger/</link><pubDate>Fri, 25 May 2007 17:06:00 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/mysql-logon-trigger/</guid><description>&lt;p&gt;With MySQL 5.0 the database provides trigger functionality on &lt;code&gt;INSERT&lt;/code&gt;, &lt;code&gt;REPLACE&lt;/code&gt;, &lt;code&gt;UPDATE&lt;/code&gt; and &lt;code&gt;DELETE&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>