[Solved] Problem with drop table

[Rafael]

After executing a drop table the .insert() methods do not create a new table, instead they try to insert as if the table still existed, even after executing .sync()

To the .insert() method work as expected and create a new table one have to execute .close() and then .open() again.

Should'nt .sync() be enough? If not, what is the rule? When to use .sync() and when reopen the table??

[Tsvetina]

Hi Rafael,

The behavior that you describe is expected, as the Data Storage engine cannot recreate a table that it has already registered as created, unless it is reinitialized. 

What the sync() method does is sync only changes made through the fluent API of the engine - inserts, updates and deletes. Since the table drop is done through a user-defined query and makes the actual database schema different from the one that the DataStorage registered on initialization, the engine is unaware of the difference. The only way to sync the changes in such scenario is to reinitialize the engine, meaning to close and open again the database connection, as you described.

Regards,
Tsvetina
Telerik

[Rafael]

Thanks for the explanation.