Idea: offer options depending of DBMS

I first tried HeidiSQL because I needed a client I can use fast for m$ SQL Server. I found it neat at first glance, so I remembered it. Now having another situation where I have to interact with a m$ SQL Server... I got some frustration, mainly driven by my lack of knowledge of it. For example, when I create a table and add a column, it suggests me to put AUTO_INCREMENT in the default value. But that won't work for SQL Server, we have to use Identity(x,y) instead... so an idea to consider (I am probably not the first one, if so, sorry for repeating), would be to adapt the suggestion relatively to the session's DBMS.

I understand that might be a lot of works since there is probably multiple place this could have impact. Still, to be as efficient as possible with multiple DBMS, that would be something HeidiSQL should consider!