Though really switching to the new storage is wiser, as eventually we should get rid of the old storage classes.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
The problem is also solved if you update the database config files, and
remove the <database> tag from mmbaseroot.xml.
Though really switching to the new storage is wiser, as eventually we should get rid of the old storage classes.
Though really switching to the new storage is wiser, as eventually we should get rid of the old storage classes.
- behaviour of max is broken in 1.7 Martijn Houtman
- Re: behaviour of max is broken in 1.7 Michiel Meeuwissen
- Re: behaviour of max is broken in 1.7 Pierre van Rooden
- Re: behaviour of max is broken in 1.7 Martijn Houtman
