I'm experiencing a strange behaviour with Telerik Data Access and the SchemaHandler CreateUpdateInfo method:
1. I create a new empty DB (SQLite) by using SchemaHandler.CreateDDLScript and ExecuteDDLScript. The DDL already contains indexes for the foreign key columns of associations.
2. I open the new DB and call SchemaHandler.CreateUpdateInfo to check for outdated schema and migration needs.
When the fluent model is unchanged, I'd expect that UpdateInfo.HasScript is false and all its properties are false, too. But in reality UpdateInfo.AddsIndexOnExistingTable is true and the script moves all content of one specific table over to a new identical table and creates the identical indexes again. All in all, a big fat expensive no-op, especially when the DB will be filled.
To me, this seems like a bug. Is it known, is there a workaround?