Bugs in PostgreSQL legacy-dbscripts

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
11/25/2007 3:08:32 AM
Gravatar
Total Posts 148

Bugs in PostgreSQL legacy-dbscripts

Hi Joe,

I'm trying to upgrade my mojoPortal-1.0.1 installation to 2.2.36 (on Mono-1.2.5.2) and I ran into a couple bugs in the legacy dbScripts.  In upgradefrom2-01to2-1.sql, around line 163, you have:

CREATE UNIQUE INDEX mp_pagemodules_pkey
    ON public.mp_pagemodules(pageid, moduleid)

INSERT INTO mp_pagemodules (pageid, moduleid, panename, moduleorder, publishbegindate )

SELECT pageid, moduleid, panename, moduleorder, current_timestamp(3)
FROM mp_modules;

The first bug is that there is ";" missing from the end of the CREATE UNIQUE INDEX statement.

The second bug is that you are selecting pageid from mp_modules, but the mp_modules table does not contain a column by that name.  What should that say?

--Dean

 

11/25/2007 6:49:39 AM
Gravatar
Total Posts 18439

Re: Bugs in PostgreSQL legacy-dbscripts

Hey Dean,

I think that the pageid was in the modules table originally and this script was for the transition when the mp_pagemodules table was created (allowing modules to be placed on more than one page), it was later that the pageid was dropped from the mp_modules table.

I'll add the semi colon.

Thanks,

Joe

12/28/2007 1:52:24 AM
Gravatar
Total Posts 148

Re: Bugs in PostgreSQL legacy-dbscripts

Yes.  I stand corrected on the pageid issue.  I think I must have run the upgrade script twice by accident.

 

You must sign in to post in the forums. This thread is closed to new posts.