Postgre Current Issues

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.
1/18/2012 9:13:39 AM
Gravatar
Total Posts 18439

Re: Postgre Current Issues

Hi Bob,

Thanks for the bug report. However, those changes only exist currently in joedev branch. No-one should be working from my development branch. I have not pushed these changes to the default branch yet because I haven't tested all my changes yet and because I haven't finished editing database scripts.

So the result will be that when I make more changes to an upgrade script before I merge it to default, then you will be missing those changes because you already ran the upgrade script and it won't run again. Once I merge changes to default then I don't edit the upgrade scripts anymore and have to make a new version incremented upgrade script to make more database changes.

When I feel my changes are stable and when I have finished editing upgrade script(s) then i will merge it to default branch. Everyone else working from the repository should be using the default branch not my development sandbox branch.

Best,

Joe

1/18/2012 8:46:34 PM
bob
Gravatar
Total Posts 126
YAF developer

Re: Postgre Current Issues

Hi, Joe.

It's my bad, as I didn't look at the branch name while updated my demo portal. It's not a problem I'll make a hack.

Thanks for the reply, bob.

 

9/19/2012 5:47:33 AM
bob
Gravatar
Total Posts 126
YAF developer

Re: Postgre Current Issues

 r.4760

In 2.3.9.1.config tinyint istead of boolean here

"moderationstatus" boolean NOT NULL,

9/19/2012 7:17:52 AM
Gravatar
Total Posts 18439

Re: Postgre Current Issues

Hi Bob,

The script has tinyint already and tinyint is the correct data type for this field.

Best,

Joe

9/19/2012 9:40:20 AM
bob
Gravatar
Total Posts 126
YAF developer

Re: Postgre Current Issues

Hi, Joe.

I don't think that Postgre has tinyint typeДразнюсь I've got an exception. I didn't look into code, maybe it should be a different data type then boolean.

Best, bob.

9/19/2012 2:39:42 PM
bob
Gravatar
Total Posts 126
YAF developer

Re: Postgre Current Issues

Update: the column should be smallint.

9/19/2012 3:15:21 PM
Gravatar
Total Posts 18439

Re: Postgre Current Issues

Thanks Bob! This is now fixed in the source code repository.

Best,

Joe

10/30/2012 5:18:45 AM
bob
Gravatar
Total Posts 126
YAF developer

Re: Postgre Current Issues

2 typos in postgre 2.3.9.3 mojoportal-core sql script  - vchar instead of varchar. 

10/30/2012 10:13:47 AM
Gravatar
Total Posts 18439

Re: Postgre Current Issues

Thanks Bob! I've fixed this in the source code repository and updated the pgsql packages for 2.3.9.3

Best,

Joe

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