On 02 Apr 09:06, Iasmini - Gmail wrote:
> Em 01/04/2014 20:46, Cédric Krier escreveu:
> >On 01 Apr 16:19, Iasmini - Gmail wrote:
> >>Em 01/04/2014 12:18, Cédric Krier escreveu:
> >>>On 01 Apr 07:59, Jon Levy wrote:
> >>>>On Tuesday, April 1, 2014 10:52:22 AM UTC-4, igomes wrote:
> >>>>>Hi,
> >>>>>
> >>>>>I'm using version 3.0 from Tryton in my computer and in server. I did a
> >>>>>backup from my database, tried to restore on server and it raises an
> >>>>>error saying that "a.password_hash" doesn't exists on table "res_user".
> >>>>>
> >>>>Try making sure update database box in the gtk's restore menu is 
> >>>>unchecked.
> >>>>I ran into one of these "doesn't exist" errors in a database restore, and
> >>>>this was
> >>>>the problem.
> >>>It is because you don't restore on the same version as the backup.
> >>>
> >>I've tried with update database checked and unchecked. The version on
> >>my machine is 3.0 and on the server too. I updated the server today
> >>to be equal of mine. On my machine I have the bank module wich is on
> >>3.0 version.
> >>I made the backup from my machine and I'm trying to restore on server.
> >>I've tried by Tryton's interface and by postgres command line. In
> >>both cases it showed the same error.
> >>
> >>How can I compare versions?
> >The password_hash field on res.user was added in the development version
> >3.1.
> >
> 
> Ok, I cloned again tryton and trytond on my machine, tried to access
> tryton client and it raises the same error.

So you probably cloned again the development version.
See the named branch migration on this mailing list or tryton-dev@.

> I updated res module
> (*./trytond -d database -u res*) and it worked.
> What is the right way to update tryton and trytond on a server? I
> have to manually run *./trytond -d database -u module* for all
> updated modules in a new version of tryton?

-u all

-- 
Cédric Krier - B2CK SPRL
Email/Jabber: [email protected]
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

Attachment: pgpN8YfSAqBzV.pgp
Description: PGP signature

Reply via email to