Home› General support

DB File Names

rtwingfield Member
in General support
I have just upgraded to v1.4.8 by installing a binary package from FreeBSD. I had tried the FreeBSD Ports technique (i.e., compile locally) but that failed well into the make process. After massive recursions up the Makefile, the process apparently duplicated the MySQL tables, but with a different naming convention. For example, zp_table-name became zenphoto_table-name.

Apparently, the new versions are propagated with the old data (as well as could be mapped . . .I suppose) and I deleted the old versions (four years old) via phpMyAdmin; however, setup still complains of unnecessary files (a huge list) and recommends deleting them. If I click on the delete button, then the Zenphoto application is broken and my only alternative is to use the FreeBSD make reinstall command, after which I can run setup again.

Where and how is this list of deprecated, erroneous, or "unnecessary" objects kept?

FYI, the old version was installed from Jun 13 2011 zenphoto-1.4.0.4.tar tarball. The new version, v1.4.8, is running with PHP v5.6. on FreeBSD 10.1-RELEASE.

Comments

  • acrylian Administrator, Developer
    For example, zp_table-name became zenphoto_table-name.
    Then the update was not done correctly. If present Zenphoto uses the existing config file in `zp-data' and the original databse prefix as set there. If not it creates a new config file and uses the default if you don't set anything else there or on Setup.

    Sorry, I have no knowledge or ever used FreeBSD ports. Installation and upgrade is explained here: http://www.zenphoto.org/news/installation-and-upgrading
    If you use other tools to install, you probably need to ask the providers of those tools.

    Direct updates from such old versions like 1.4.0.4 is not recommended. Please see link above.
  • rtwingfield Member
    . . .regardless, is zenphoto_table-name the new naming convention?

    . . .and yes, I've already read the caveats about updating old version, but examination via. phpMyAdmin reveals that the data were converted.
  • rtwingfield Member
    OK . . .discovered this nuance in ./zp-data/zenphoto.cfg.php

    `
    // If you're sharing the database with other tables
    (and of course you probably are . . .because it's a MySQL database),
    use a prefix to be safe.
    $conf['mysql_prefix'] = "zenphoto_";
    `
    .
    so if I understand this, then if you were to change "zenphoto_" to "foobar_", then the DB files would be named "foobar_table-name".

    I'm not sure if and when or how setup may update (if at all) this value in the file. In fact, during my earlier upgrade-conversion attempts, I did not select the "zenphoto_" prefix.

    OTTF,
    RW
    (http://archaxis.net/htdocs/RTWingfield/htdocs/humor/OTTF/OTTF.html)
  • acrylian Administrator, Developer
    Exactly. you can choose for the prefix what ever you like. That way several ZP installs can share a database or with completely different systems.

    There is no naming convention except the MySQL naming conventions.

    IF you upgrade you just need to make sure you use the same prefix in case you deleted the config file. Otherwise you get fresh tables. But you can switch it back anytime to use the old ones again.

    I'm not sure if and when or how setup may update (if at all) this value in the file. In fact, during my earlier upgrade-conversion attempts, I did not select the "zenphoto_" prefix.
    It does not happen if you upgrade the way we describe. If may and did happen with install helpers frequently in the past (seems to be working now on some though). Also upgrading from old version can cause troube because the name of the file and the place of storage changed over the years.
Sign In or Register to comment.