Bug: mp_Pages_SelectOne should return 2 values

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.
9/29/2006 4:55:13 AM
Jan Hussaarts
Gravatar
Total Posts 73
View Posts

Bug: mp_Pages_SelectOne should return 2 values

Bug?

After installing the new version of Mojo, I run the upgradescript: upgradefrom212tonext for MSSQL. I tried to access mojoportal. I received an error and was able to trace it back to dbPortal.cs. It appears that the stored procedure mp_Pages_SelectOne should return 2 values whereas the old version only returns one value. Looking at the createprocs script, I noticed that that version of mp_Pages_SelectOne returns 2 values. I also notices that this stored procedure is not encorporated in the upgrade script.

I will run the create stored procs script; I expect that that will solve the problem.

Regards,

Jan

9/29/2006 5:02:30 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Bug: mp_Pages_SelectOne should return 2 values

That script is a development script for the next version, it is not complete or finalized and should not be used. Its just my work toward the upgrade script for the next version and is subject to change. If doing a clean install there is no need to run any upgrade scripts at all. There is no schema change between 2.1.1 - 2.1.3, there are stored proc changes but there is no upgrade just run the stored proc script and you have the latest.

Sorry for any confusion by the presence of that script, its not in the release version, just in source and it needs to stay in there (at least in svn) so I can work on it.

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