#2764 Upgrade from 4.2.3 loses users/accounts

Greg Roach

In PostGres databases, the upgrade from 4.2.3 (or earlier) to 4.3.0svn fails to copy the user details from the old pgv_users account to the new pgv_user/pgv_user_setting/pgv_user_gedcom_setting tables.

This is because the PGV_DB::table_exists() function is broken for postgres.

Everything is OK in MySQL and SQLite.

Does anybody know how to query the data-dictionary in PostGres?


  • Greg Roach

    Greg Roach - 2010-01-22
    • summary: Upgrade from 4.2 loses users/accounts --> Upgrade from 4.2.3 loses users/accounts
  • Greg Roach

    Greg Roach - 2010-01-25

    This problem has been fixed in SVN.

    Please can you check that the fix works for you.

    If you agree that the problem is fixed, you should change the bug status to "Closed".

    If you think the problem is not fixed, please provide further information.


    The PGV Team

  • Greg Roach

    Greg Roach - 2010-01-25

    Updated code to check information schema

  • Greg Roach

    Greg Roach - 2010-01-25
    • assigned_to: nobody --> fisharebest
    • status: open --> closed-fixed
  • Meliza Amity

    Meliza Amity - 2010-02-28

    I uploaded today to my production site the SVN changes 6695 or 6696 (after 2010-01-08) till 6942.
    My DB is MySQL.

    I see my users in the old users table.
    I see my users in the new user table.
    user_gedcom_setting is empty.
    user_setting shows
    sessiontime of user_id 0
    language as english for user_ids 1-463. The language should not be english for
    I had to define a new admin user after the PGV files were changed. I see the definitions of this new user 464 in the table.

    My test site workes OK with its few users.

    What went wrong on the production site and how can I get the users to work again ASAP?
    I hope I do not need to fill the table using PhpMyAdmin from the users table.


  • Meliza Amity

    Meliza Amity - 2010-02-28
    • priority: 7 --> 9
  • TomekJ

    TomekJ - 2014-01-30

    I have the same problem with upgrade from 4.1.5 to 4.2.4 stable. MySQL version 5.0.51.
    Problem is in file
    at line 152 with UNION ALL and INSERT to table user_setting.



Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks