Make trigger editor compatible to MSSQL about heidisql

[ansgarbecker]

Could you please provide the very last 3 or 5 SQL queries from the log panel at the bottom when the crash dialog happens? Screenshot would be nice.

[Alexsey]

[Alexsey]

Now, looking in to query log, I understand that this is what I should be posted in the first place :)

[ilpssun]

I think the correct way to handle this would be to just display a notice that heidi is not yet capable of editing MSSQL triggers. That would be fine by me. It is, however, annoying that Heidi crashes when I accidentally click on the wrong icon in the list of tables/views/triggers.

The optimal solution, of course, would be to support MSSQL triggers.

If you would like to list all triggers, use a statement like this:

select
    -- s.name as table_schema,
    -- USER_NAME(sysobjects.uid) as trigger_owner,
    OBJECT_NAME(parent_obj) as table_name,
    case
        when OBJECTPROPERTY( id, 'ExecIsUpdateTrigger') = 1 then 'Update'
        when OBJECTPROPERTY( id, 'ExecIsDeleteTrigger') = 1 then 'Delete'
        when OBJECTPROPERTY( id, 'ExecIsInsertTrigger') = 1 then 'Insert'
    end as trigger_type,
    s.name as schema_name,
    sysobjects.name as trigger_name

    /*
    OBJECTPROPERTY( id, 'ExecIsAfterTrigger') as isafter,
    OBJECTPROPERTY( id, 'ExecIsInsteadOfTrigger') as isinsteadof,
    OBJECTPROPERTY(id, 'ExecIsTriggerDisabled') as [disabled]
    */
from sysobjects

inner join sysusers
    on sysobjects.uid = sysusers.uid

inner join sys.tables t
    on sysobjects.parent_obj = t.object_id

inner join sys.schemas s
    on t.schema_id = s.schema_id

where sysobjects.type = 'TR'
order by table_name

With that info, you can use schema and trigger name in the following query to get the trigger definition:

SELECT OBJECT_DEFINITION (OBJECT_ID(N'schema.trigger_name')) AS [Trigger Definition];