> > > This is not to say that MySQL could not have more of the file management > features. For example, the ability to add or remove datafiles on the fly > and the > ability to detach tablespaces as collections of tables.
That's where MySQL(read InnoDB) got stuck actually, it never introduced a powerful datafiles management system, and that is where Oracle excels (as far as being almost a O.S.) with multiple level of abstractions, just think of ASM. It is actually the part of Oracle I like most as well as the really "oraclish" way to get stats out of it! The 'problem' with MySQL is that it is so easy to start with it that people do not realize that is also a real RDBMS. -- Claudio Making innodb tablespaces default... well, it still would not liberate the > users > from thinking whether they want to run with them enabled or not. For > example, > if I have 10000 tables of 100 bytes each, I probably do not want > tablespaces. > If I have 1% of tables consuming 99% of the space, I would also not want > the > tablespaces. > > As for the OP's problem, unless he changed his mind about the need to > import, > the same amount of space would anyway be consumed. The solution would > probably be to find some bigger O Sdisk and copy that ibdata file there. > Right? > > > Cheers > Karen > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql > > -- Claudio
