~openerp-chinese-team/openobject-doc/Chinese-init

.. i18n: You can skip minor versions, for example, you do not need to install all the intermediary versions between 6.0.6 and 6.0.15 if you need to upgrade an outdated installation, as long as you stay in the same version line (6.0 in this example).

.. note:: Minor Versions

You can skip minor versions, for example, you do not need to install all the intermediary versions between 6.0.6 and 6.0.15 if you need to upgrade an outdated installation, as long as you stay in the same version line (6.0 in this example).

.. i18n: Updating an existing OpenERP installation to a newer patch release boils down to 2 operations:

Updating an existing OpenERP installation to a newer patch release boils down to 2 operations:

.. i18n: * Install the new code over the existing one

.. i18n: * Synchronize each existing database with the new code

* Install the new code over the existing one

* Synchronize each existing database with the new code

.. i18n: In order to accomplish this, the following step-by-step procedure should give you

.. i18n: the best results:

In order to accomplish this, the following step-by-step procedure should give you

the best results:

.. i18n: #. Make a fresh backup of all existing databases, as well as a backup of the files

.. i18n: of your OpenERP installation (server and addons), just in case.

.. i18n: #. Stop the OpenERP server.

.. i18n: #. Update the source files to the latest release, or simply install the new releases

.. i18n: over the previous ones. If need be, you can uninstall the previous version, but

.. i18n: be sure to avoid uninstalling PostgreSQL, as this could delete

.. i18n: your current databases!

.. i18n: #. Locate the separate server executable ``openerp-server.exe`` (this is not the

.. i18n: executable used by the Windows Service!). It should be in the location where

100

.. i18n: you installed OpenERP Server, for example in ``C:\Programs\OpenERP 6.0\Server``.

101

.. i18n: #. From a Command-Line Prompt, start the server executable manually (directly call

102

.. i18n: the executable you located above), with the following parameters, to trigger an

103

.. i18n: update of all module data and views in the database, based on the new source files

104

.. i18n: (include your usual startup parameters, if any, and replace ``DB_NAME`` with the name

105

.. i18n: of the OpenERP database you wish to update)::

106

.. i18n:

107

.. i18n: openerp-server.exe -d DB_NAME -u all

108

.. i18n:

109

.. i18n: #. Let the server complete its startup (watch the log file for the final message that

110

.. i18n: says ``OpenERP server is running, waiting for connections`` or wait until you can

111

.. i18n: connect to that database with a GTK client), then stop the server using the :kbd:`Ctrl+C`

112

.. i18n: key combination and repeat previous step for each database on this OpenERP installation

113

.. i18n: (any database not updated will use the latest business logic but might have errors

114

.. i18n: or missing improvements in the views until you update it using this procedure).

115

.. i18n: #. Stop the server again with :kbd:`Ctrl+C` and restart it normally as a service.

116

.. i18n: #. You can now proceed with the update of the GTK clients, which can be done

117

.. i18n: separately by simply reinstalling the latest version over the previous one.

118

119

120

#. Make a fresh backup of all existing databases, as well as a backup of the files

121

of your OpenERP installation (server and addons), just in case.

122

#. Stop the OpenERP server.

123

#. Update the source files to the latest release, or simply install the new releases

124

over the previous ones. If need be, you can uninstall the previous version, but

125

be sure to avoid uninstalling PostgreSQL, as this could delete

126

your current databases!

127

#. Locate the separate server executable ``openerp-server.exe`` (this is not the

128

executable used by the Windows Service!). It should be in the location where

129

you installed OpenERP Server, for example in ``C:\Programs\OpenERP 6.0\Server``.

130

#. From a Command-Line Prompt, start the server executable manually (directly call

131

the executable you located above), with the following parameters, to trigger an

132

update of all module data and views in the database, based on the new source files

133

(include your usual startup parameters, if any, and replace ``DB_NAME`` with the name

134

of the OpenERP database you wish to update)::

135

136

openerp-server.exe -d DB_NAME -u all

137

138

#. Let the server complete its startup (watch the log file for the final message that

139

says ``OpenERP server is running, waiting for connections`` or wait until you can

140

connect to that database with a GTK client), then stop the server using the :kbd:`Ctrl+C`

141

key combination and repeat previous step for each database on this OpenERP installation

142

(any database not updated will use the latest business logic but might have errors

143

or missing improvements in the views until you update it using this procedure).

144

#. Stop the server again with :kbd:`Ctrl+C` and restart it normally as a service.

145

#. You can now proceed with the update of the GTK clients, which can be done

146

separately by simply reinstalling the latest version over the previous one.

147

148

.. i18n: .. note:: Server

149

.. i18n:

150

.. i18n: As an alternative to restarting the server in update mode for each database, as described above, you may try to start the server normally after installing the new version, and then connect to each database as the *Administrator* user, open the list of modules and manually trigger an update of the *base* module.

151

.. i18n:

152

.. i18n: Because all modules depend on *base* they will be updated too. However this requires the *Administrator* password of each database and may not work for some updates, specifically when the update prevents you from logging into the system.

153

154

155

.. note:: Server

156

157

As an alternative to restarting the server in update mode for each database, as described above, you may try to start the server normally after installing the new version, and then connect to each database as the *Administrator* user, open the list of modules and manually trigger an update of the *base* module.

158

159

Because all modules depend on *base* they will be updated too. However this requires the *Administrator* password of each database and may not work for some updates, specifically when the update prevents you from logging into the system.

160

161

.. i18n: .. tip:: Developer Book

162

.. i18n:

163

.. i18n: For more technical details on the actual operations accomplished by the server during such an update, you may refer to the corresponding section in the Developer Book: :ref:`technical_update_procedure`.

164

165

166

.. tip:: Developer Book

167

168

For more technical details on the actual operations accomplished by the server during such an update, you may refer to the corresponding section in the Developer Book: :ref:`technical_update_procedure`.

169

170

.. i18n: Going to a Newer Major Release

171

.. i18n: ++++++++++++++++++++++++++++++

172

173

174

Going to a Newer Major Release

175

++++++++++++++++++++++++++++++

176

177

.. i18n: OpenERP's release policy states that one or two major releases are published from the

178

.. i18n: development version every year. Transitioning to the next major release implies a lot

179

.. i18n: more changes than jumping to another minor release.

180

.. i18n: As the underlying OpenERP data structures usually evolve quite a bit from one major release

181

.. i18n: to the next, a full migration of the existing data is needed.

182

.. i18n: Each major release will be published with specific recommendations and procedures for

183

.. i18n: upgrading an existing OpenERP system to the next major version.

184

185

186

OpenERP's release policy states that one or two major releases are published from the

187

development version every year. Transitioning to the next major release implies a lot

188

more changes than jumping to another minor release.

189

As the underlying OpenERP data structures usually evolve quite a bit from one major release

190

to the next, a full migration of the existing data is needed.

191

Each major release will be published with specific recommendations and procedures for

192

upgrading an existing OpenERP system to the next major version.

193

194

.. i18n: .. note:: Major Release

195

.. i18n:

196

.. i18n: For major releases, it is usually not possible to skip one release, for example upgrading directly from OpenERP 4.2 to OpenERP 6.0. If you need to do such an upgrade, you will simply have to do each intermediary upgrade one after the other.

197

198

199

.. note:: Major Release

200

201

For major releases, it is usually not possible to skip one release, for example upgrading directly from OpenERP 4.2 to OpenERP 6.0. If you need to do such an upgrade, you will simply have to do each intermediary upgrade one after the other.

Older »