Hi, Erik. Apparently I am not migrating this properly. The version from the SQl select command was 1.3.30.

I moved the database by doing "pg_dumpall -c > dumpdata" from the 1.3.30 system but using the pg_dumpall program from the 1.5.3 system. I then issued "psql -f dumpdata postgres" on the 1.5.3 system. Then logging into the 1.5.3 system with psql and executing a "\l" shows all of the databases. BUT, the version field from default is 1.3.30

Very odd the every select I tried on the database works correctly even though the version is the old version.

How should I proceed? Can I just use SQl to modify the version field, or would that just be making things worse?


Regards,
Bill Ott

Home: 919-363-0031
Cell: 919-434-7589
Email: Mailto:bill...@theotts.org
Website: http://www.theotts.org
Profile: http://www.linkedin.com/in/wbott


On 02/27/2017 01:10 PM, Erik Huelsmann wrote:
Hi Bill,

On Mon, Feb 27, 2017 at 6:28 PM, bill Ott <bill...@theotts.org <mailto:bill...@theotts.org>> wrote:

    I have successfully moved the database from ledgersmb 1.3.30
    (postgresql 9.1.7)  to ledgersmb 1.5.3 (postgresql 9.5.6). I can
    do SQL selects in either and get the same results.


Great news! Thanks for sharing!

      When I attempt to access the database from ledgersmb 1.5.3 I get
    an error saying that the is a Database mismatch.


"database mismatch" (or rather database match) is determined by looking at the value in the output column if you run this query:

   SELECT * FROM defaults WHERE setting_key = 'version';

What is the output this statement in your setup?

    The documentation hints "Please reload the templates into the
    database after upgrading to 1.5. The database maintenance utility
    |setup.pl <http://setup.pl>| offers this functionality through
    it's "Load Templates" button. I cannot find the referenced
    button.  Any help appreciated.



While this advice is correct, it's not helpful in your case. It's talking about the templates in the database from which invoices are printed. These used to be stored on disk and now have to be loaded in the database. The upgrade process *should* take care of that.


The advice you're looking for is that you can log in into your database through setup.pl <http://setup.pl> and click the "Rebuild" button. That *should* resolve your issue, but I'm still very interested in hearing what the version number is that the query above reports.


--
Bye,

Erik.

http://efficito.com <http://efficito.com/> -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot


_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Ledger-smb-users mailing list
Ledger-smb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users

Reply via email to