| Thread Previous • Date Previous • Date Next • Thread Next |
Hi,Maybe a transitional setting that would create/update both the "legacy" frm file and a file with the new format when required could be a solution for backward compatibility.
In that case, it would read the new format definition file if present.Another possibility could be that we could choose the default format and only newly created tables would use that format but it wouldnt modify the existing ones (or maybe via an ALTER).
It also could be of use to have a tool that could offline convert the files between the two format in case MariaDB would have to be downgraded or replaced by MySQL or another fork that does not support the new definition file format.
Regards. Le 10/07/2013 08:37, Sergei Golubchik a écrit :
Hi, Roberto! On Jul 10, Roberto Spadim wrote:2)why we "still" with this "old" unireg format?That was in the agenda for *at least* 10 years. May be 15 already. Like "it's simple, let's do it next month, shouldn't take more than a couple of weeks". Still, never happened.i know that someone must start the new format and it will not be compatible with mysql... but there's any raw idea or a issue in mdev or lauchpad about changing .frm format or creating a new one?Yes, create a view and look at its frm file. The code for writing and reading new frm files is already there. Regards, Sergei
| Thread Previous • Date Previous • Date Next • Thread Next |
