(w/my FIX) Re: [freeside] schema problems encountered while upgrading from 1.4.1 to 1.5.1pre5
mailinglists-freeside at sisna.com
Mon Oct 18 12:01:53 PDT 2004
My email claimed this was 1.5.1pre5, when it was really 1.5.0pre5.
The solution is to replace _temp_ with _ for the two entries mentioned.
I solved the problem by installing 1.5.0pre5 as if it were a new install. I
was using different database names for each release anyhow, so it wasn't
difficult to keep them isolated. After the freeside-setup part, I dumped the
database to a backup (I considered I'll never need it, but what if?). droped
and recreated the database, then reloaded. After the last steps were
complete, it's up and running.
Ivan, do you have any comments on this? Is this the correct solution? Is
there anything you want me to verify at this point?
I do notice the configuration of email templates and preferences are missing.
Is this data in flat files? (I recall they are...)
ps, you may know me as supaplex on OFTC, or at http://www.daxal.com/.
On Friday 15 October 2004 01:19 pm, Scott wrote:
> I'm following http://www.sisd.com/freeside/devdocs/upgrade10.html.
> So far I was able to do everything w/o a hitch. I'm in the process of
> upgrading my existing 1.4.1 install to 1.5.1pre5. Currently I only have
> the database to work with (more on that if neccessary). Consider this a
> fresh install on a new drive, with restores from backups on the database.
> I'm using Pg 7.5.1 on debian sarge/testing. (my last apt update was no more
> then 2 days ago).
> I run into problems where the docs say "then reload".
> the freeside151pre5 database is empty prior to:
> freeside at fs:~$ psql -e freeside151pre5 <
> And a moment or two later, it's all ended with: (non relavant success
> omitted) SELECT pg_catalog.setval('part_pkg_temp_pkgpart_seq', 29, true);
> ERROR: relation "part_pkg_temp_pkgpart_seq" does not exist
> SELECT pg_catalog.setval('h_part_pkg_temp_historynum_seq', 102, true);
> ERROR: relation "h_part_pkg_temp_historynum_seq" does not exist
> Can i safely ignore these errors, or is there something else I should do
> before proceeding?
More information about the freeside-users