Hi, Well, the plan was that ANALYZE is quick by default, so no progress bar is required. But if a progress bar is required, I think it would also be required for other queries (because ANALYZE internally is a list of queries). It could be done I guess, but it wouldn't very accurate.
Could you try to find out why ANALYZE is slow in your case? Is there one table that uses most of the time, or do all the table use about the same time? Do you just run "ANALYZE" (without parameters)? > Is this a patch you'd consider adding to the trunk? Let's first analyze what the problem is. If there is no other way to solve it, then I guess it makes sense to try. Regards, Thomas -- 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.
