Hi Frank, Am Samstag, den 05.01.2008, 22:41 +0100 schrieb Frank Schönheit - Sun Microsystems Germany: > Hi Marc,
> > Only one observation makes me think: Using "shutdown compact" from the > > SQL window lead to closing the session, no data was accessible after > > running this command. IIRC that was different in the last release > > version I tried (2.3.1). I think using that one anything worked without > > re-opening the .odb file (that helped), but I'm not really sure what is > > right and what's wrong: > > > > The ordinary user would be happy to have it's tables connected after > > compacting the database. But in fact a SQL command named "shutdown" that > > shuts down the database is doing what it is asked for. > > I don't think I touched anything in this area, but maybe there were > other changes between 2.3.1 and m238 (which is what this milestone is > based on). > > For the behaviour as such: For one, it's absolutely undefined at the > moment how the UI should behave when you shut down via direct SQL. That > said, I also tend to think the requirement to close and re-open the .odb > makes sense. That's fine with me. I could eventually imagine having an action (menu entry, button or so) that triggers compacting an internal HSQL database in a controlled way (closing open windows, running "shutdown compact", re-open the existing connection. At least nice to have as for dbase ... sounds like I'd write an issue. Lastly I was copying one table having 6 or 7 mixed type rows and 2^16 records from a running 2.3.1 over to the macro.M1. After that I had to set a primary key on the new table and when I was through the .odb file on disk was ~17 MB big. Compacting shrunk it to ~5 MB. Thanks, Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
