Hi, unfortunately not. Sorry for not having mentioned but I'm using the latest build.
I fill a normal table (A) using a temporary table (B) based view (a join on two temp tables, see my post above for detailed information). After A is filled, I create an index on A: 1. If I've dropped B before, the index on A is normally created (total size of database: 17MB). 2. If I haven't drop B Before, the index on A becomes much too large (total size of database: ~100MB). If I then drop the index, the size of the database is 13MB. So the netto weight of the index is some 87MB. This seems to be a bug. Regards, Philipp > > can "solve" the problem, if I drop both temporary tables > > Is your question why temp tables are not deleted automatically when > the database is closed? This was a bug, it was fixed in version > 1.2.135 (2010-05-08) - see the change log "Global temporary tables are > now deleted when closing the database. Before, they were deleted when > opening the database the next time." -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
