# 2963 Restoring a Database Can Cause Issues if New Tables Were Added Since Backup

---

I found an issue creating a table after restoring a backup. You can reproduce the problem following this steps:

1. Take any database and do a backup saving the catalog.
2. Create a new table in the same database
3. Insert some rows into it
4. Restore the backup, restoring the catalog.
5. The table created in step 2 is lost, as expected.

Now the problem:

- If you recreate the lost table using exactly the same structure, the newly created table will contain the rows added before it was created, which is an unexpected behavior as a newly created table is expected not to contain any data.

- If you try to create a table with a different structure but with same name you will never succeed because an exception will be raised.

I suspect I know why it is happening - it's because after the restore the catalog was recreated but the data and index files remained in the database directory so when the table is recreated it's using those files, however I think it would be better to overwrite those files when the table is created again.