• Forums
  • Bug Reports
  • BlogArchiveView is not showing any matching results when using PostgreSQL

BlogArchiveView is not showing any matching results when using PostgreSQL

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.
8/9/2005 5:55:57 PM
Todd Stone
Gravatar
Total Posts 45
View Posts

BlogArchiveView is not showing any matching results when using PostgreSQL

BlogArchiveView is not showing any matching results when using PostgreSQL.

An example is at http://demo.mojoportal.com.  Try selecting a prior months blog entries and BlogArchiveView.aspx will not display any results for the month.

8/10/2005 12:37:03 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: BlogArchiveView is not showing any matching results when using PostgreSQL

I'll look into it, most likely a problem in a stored procedure.

Thanks,

Joe
8/10/2005 1:14:25 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: BlogArchiveView is not showing any matching results when using PostgreSQL

This is now fixed in svn, it was an erro in the stored procedure, the parameters were flipped, it wa passing month for year and year for month. You can get the latest stored proc script from svn and run it to fix.

Thanks,

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