Ignore:
Timestamp:
Apr 21, 2016, 1:13:30 PM (7 years ago)
Author:
Nicklas Nordborg
Message:

References #2002: Change history logging should use batch API instead of Hibernate

The LogControl class now uses a PreparedStatement with SQL from the configuration files. The large test case from #2000 seems to be improved by 1-2 minutes.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/config/dist/mysql-queries.xml

    r7121 r7132  
    6262  </query>
    6363 
     64  <query id="DBLOG_INSERT_INTO_CHANGEHISTORYDETAILS" type="SQL">
     65    <sql>
     66      INSERT INTO [ChangeHistoryDetails]
     67        ([version], [history_id], [change_type], [item_id], [item_type], [change_info], [old_value], [new_value])
     68      VALUES (0, ?, ?, ?, ?, ?, ?, ?)
     69    </sql>
     70    <description>
     71      SQL query for inserting rows into the ChangeHistoryDetails table.
     72      The primary key (id) must be auto-generated.
     73      Parameters: history_id, change_type, item_id, item_type, change_info, old_value, new_value
     74    </description>
     75  </query>
    6476
    6577
Note: See TracChangeset for help on using the changeset viewer.