Deleting all the data in the database (i.e. dropping all the tables)
should be sufficient, no? There's nothing to store if you don't have any
data in the database (in particular, there's no reason to store the
version as far as I can tell -- you can just act as if the user deleted
the database as soon as the database is empty).
Well, I thought about that already, but that's an optimization that can be
done by the user agent. Should a specification suggest low level
optimizations ?
Its also needed to delete views. Tables is not enough, and currently I'm
not thinking of anything else.
So developers need to be educated: drop all tables, drop all views.
Would be much more simple to just delete the database explicitly, and
should be straightforward for most implementations given that those also
need to support their delete private data functionality.
