Santo Leto
HoneySoftware CTO & VP of Sales

My name is Santo Leto and as of today I’m a three years experience MySQL™ DBA and Developer.

I graduated in physics from Trieste University (Italy) with a thesis on Grid Computing and today I deal mainly with developing and RDBMS.

I’m 26 y.o. and I live in Trieste, in the north-east of Italy, where I work from home and where I am attending a two-years part-time MBA in International Business.

My interests, among others, are MySQL™, RDBMSs, Database Cluster, High Availability and Cloud Computing. I like Country music and vocal Jazz that I typically listen from last.fm and new92.com.

I am a “member” of the MySQL™ Community as well as a MySQL™ Enterprise (paying/not paying) Customer. I like the MySQL™ Server, and, in general, the MySQL™ “World”. I do try to actively participate in the Community testing new features and releases, submitting bug reports, feedback and sharing my thoughts. This blog is aggregated by the Planet MySQL™ and some posts also appear on the Planet MySQL™ with Sun™ Products.

In general I am SUN™ “oriented” but I do like Microsoft™ as well. I am not a fanatic of Open Source nor a fanatic of Closed Source since I think that the “Open vs Closed” conflict is not productive, and I do try to be moderate.

I am CTO of HoneySoftware, a Company whose mission is the design and development of GUI Tools for MySQL™ Administration & Monitoring and I’m also the HoneySoftware’s webmaster and the one who takes care of the international relationships of that Company.

As Leader and main programmer of the HoneyMonitor Project - HoneyMonitor is our GUI for MySQL™ - I am responsible for creating the development road map, implementing and testing new features, scheduling releases, prioritizing issues and support requests.

I’m also in charge of coordinating Q.A.

The following is the list of my verified MySQL™ Bugs (#1 is the most recent):

• #42473 - Non Critical - Server: Packaging - Can’t download version 6.0.9-alpha (unzip in C pkg)
• #42011 - Feature request - Server: Replication - Add a File_date column in the output of SHOW BINARY LOGS
• #42010 - Serious - Server: Docs - CHM Manual - Full Text Search not included
• #41975 - Feature request - Client - Support for SSL options not included in mysqlbinlog
• #41943 - Serious - Client - mysqlbinlog.exe crashes if –hexdump option is used
• #41797 - Serious - Server: UDF - Server crashes when calling a UDF created with a wrong return data type
• #41771 - Serious - Server: I_S - Can’t retrieve data type attributes of routine parameters
• #41766 - Non Critical - Server: Docs - Broken links in the chm file
• #41718 - Serious - Server: Docs - FALCON_TABLESPACES isn’t included
• #39133 - Serious - Server: Replication - Changing the engine of log table breaks replication
• #38913 - Non Critical - Server: Docs - Variable maria_recovery does not exist
• #38907 - Non Critical - Server: Packaging - Manual (.chm) corrupted
• #38284 - Serious - Server: Packaging - Data directory is not included in v.6.0.6-alpha-debug-backup-0.5-win32
• #37567 - Feature Request - Server: SP - `information_schema`.`TRIGGERS`.`CREATED` is always NULL
• #37187 - Non Critical - Server: Replication - `INFORMATION_SCHEMA`.`GLOBAL_VARIABLES`: inconsistent status
• #37030 - Non Critical - Server: Falcon - Can’t find a Falcon TableSpace if no Falcon Tables are using that TableSpace
• #35994 - Feature Request - Server: Replication - Support for the table information_schema.SLAVE_STATUS
• #35981 - Serious - Server: SP - ALTER EVENT causes the server to change the PRESERVE option
• #35432 - Non Critical - Server: Maria - Can’t set maria_pagecache_buffer_size at runtime
• #35333 - Critical - Server: Federated - If a Federated Table can’t connect to the remote host, can’t retrieve metadata
• #35210 - Serious - Server: I_S - Can’t filter Falcon Tables by TableSpaces at command-line
• #35192 - Serious - Server: Docs - Six system variables are not shown as result of the SHOW VARIABLES
• #35175 - Serious - Server: General - SHOW FUNCTION STATUS returns an error if no database is selected
• #33488 - Non Critical - Server: Packaging - Help tables in mysql database are empty
• #33455 - Feature Request - Server: I_S - Can’t retrieve Routine Parameters if the user has limited privileges
• #33287 - Serious - Server: I_S - Can’t retrieve Partition Comment, if the Table has Subpartitioning
• #33106 - Serious - Server: I_S - Can’t distinguish parameters in information_schema.parameters
• #32842  - Serious, Duplicate - Server: Views - If ALTER VIEW spans more rows VIEW_DEFINITION is incorrect updated
• #30837 - Non Critical - Server: General - Variables are listed twice by SHOW VARIABLES
• #30826 - Serious - Server: Partition - Falcon - OPTIMIZE PARTITION not supported
• #30695 - Critical - Server: Partition - Apostrophe in PARTITION clause comment crashes the server
• #30671 - Serious - Server: Federated - ALTER SERVER causes the Server to crash
• #29768 - Serious - Server: SP - ALTER EVENT .. RENAME TO .. drops the event if event_scheduler is ON

Looking at the bugs above, you will note that some of them are tagged as “Can’t repeat”.

If you post a bug and it is immediately tagged as “Can’t repeat” it means that probably you didn’t write a good Bug Report - i.e. it is difficult for developers or support engineers to reproduce the bug using the information included in your report. Hovewer, a bug can be permanently tagged as “Can’t repeat” in other, less unpleasant, cases. For example, a bug can be verified (over the latest version of the Server) and then fixed indirectly by fixing other bugs. In this case you probably wrote a good bug report even if the status of your bug is “Can’t Repeat”. It’s just a way to close the opened issue in the Bug Tracking System by saying: “this bug is not a bug anymore because of other changes we did either in code or in the analysis of the project”.

My complete C.V. is available here: ITA | ENG (those are password protected links: please feel free to request me username and password).

My BS thesis (Italian only) is here.

For all log enthusiasts, I keep a what-I-am-doing slow-life-log, on Twitter - here.

I have a page on FaceBook, here, and, if you want to know where I am right now, you can try click here.

I am sleto on Flickr™ and santoleto on del.icio.us.

I have also a Life Weblog (Italian + English) here.

If you want to know all about my social network activities, you can glance at the aggregators http://friendfeed.com/sleto and http://sleto.mp.

My Skype™ user name is santo_leto. You are welcome to contact me or drop me a line:

pub 1024D/0B6F63DF 10/08/2007 Santo Leto <sales@honeysoftware.com>
Primary Key Fingerprint: 5E56 FFBE 320B 6A05 0D89 55A4 40A7 9981 0B6F 63DF
Public Key: http://www.honeysoftware.com/pubkey/sleto/Santo_Leto_PubKey.asc