[opencms-dev] Better not using PostgreSQL 8 anymore?

[Ivan Codarin]

Dear All,
I'm trying to have postgresql working at two levels:
1. junit tests are now working in the development branch (not in the 
6.2beta). Tests on group/user deletetion are running successfully.
2. setup wizard: last night I created a different setup wizard where I 
fixed some problems.

The template1 being accessed by other users persists because (i think) 
the connection pooler is locking  the template.
But if you enter all the correct data  the first time 
(dbname,dbuser,templatename) and you never press "back" all runs smoothly.
If you need to change the setup you have to re-start postgresql/tomcat 
(I think this will not be solved for the 6.2 release).

*This happens on the development branch  (6.1.11) that isn't the 
6.2beta, so you can try it only checking out from cvs when Alkacon's 
team will commit it!*
I solved another bug regarding the database name that in the previous 
versions should be the same as the username.

I posted (sometime ago) a little tutorial on how to install 6.2beta on 
postgresql... try to search on the mailing list (subject like postgresql 
6.2beta).

I hope to agree with Alkacon team on these changes on the setup classes 
and steps to release this features for the 6.2 at the end of this week 
(and fixes for 6.2.1).

Regards
Ivan
 

Jack Bakker wrote:
> That is good news for me too. Thanks Ivan. 
>
> I just installed 6.2 beta for the first time for use with PostgreSQL 7.4.x.
> I noted the setup wizard still is not working as one would hope. Haven't had
> the chance to test with PostgreSQL 8 (sorry Ivan). Not sure if the wizard
> bugs have been resolved. In case they haven't yet: 
>
> Ivan and Andreas pointed out ideas relating to the setup wizard for
> PostgreSQL. 
> http://mail.opencms.org/pipermail/opencms-dev/2006q1/022605.html
>
> My way around (for PostgreSQL 7.4.x) was different:
>
> - prior to installation: create the db; create the opencms db user
> - choose template1 for the template database
> - enter connection string without database name
> - enter the database name
> - choose to create user and tables
> - view the errors including the one on template1 being accessed by other
> users
> - since one can't continue with errors, I cut and paste into the URL the
> next step: /step_6_module_selection.jsp 
>
>  
>
>
> ..............................
> Jack Bakker 
> -----< www.iable.ca >---------
>  
>
>   
>> -----Original Message-----
>> From: opencms-dev-bounces at opencms.org 
>> [mailto:opencms-dev-bounces at opencms.org] On Behalf Of 
>> Alexander Kandzior
>> Sent: March 22, 2006 5:39 AM
>> To: 'The OpenCms mailing list'
>> Subject: RE: [opencms-dev] Better not using PostgreSQL 8 anymore?
>>
>>
>> Thanks to Ivan Codarin, there is a good chance that the 
>> issues with with PostgeSQL 8 are solved in the upcoming 6.2.0 
>> release. According to Ivan, all Junit test work fine.
>>
>> Kind Regards,
>> Alex.
>>
>> -------------------
>> Alexander Kandzior
>>                                                                
>> Alkacon Software GmbH  - The OpenCms Experts                        
>> http://www.alkacon.com - http://www.opencms.org               
>>  
>>
>>     
>>> -----Original Message-----
>>> From: opencms-dev-bounces at opencms.org 
>>> [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Uhlig, Roman 
>>> Knuepfer Verlag
>>> Sent: Wednesday, March 22, 2006 10:47 AM
>>> To: The OpenCms mailing list
>>> Subject: [opencms-dev] Better not using PostgreSQL 8 anymore?
>>>
>>>
>>> Hi,
>>>
>>> I'm currently planning the migration of our OpenCms 
>>>       
>> installations to 
>>     
>>> our new servers and find myself confronted with the 
>>>       
>> question, whether 
>>     
>>> I should still use PostgreSQL 8 for it.
>>> >From my point of view the bugs and problems are adding up,
>>> e.g. I still
>>> can't delete users with OpenCms 6.0.4. All these problems start to 
>>> have a serious impact on the usability of OpenCms in 
>>>       
>> connection with 
>>     
>>> PostgreSQL 8.
>>>
>>> What do you think: Is there room for hope for a maintenance of the 
>>> PostgreSQL 8 implementation, or should I switch to another database 
>>> (which would be a pain, since we are only using PostgreSQL 8 on our 
>>> online servers)?
>>>
>>> Best regards,
>>> Roman
>>>
>>> _______________________________________________
>>> This mail is sent to you from the opencms-dev mailing list 
>>>       
>> To change 
>>     
>>> your list options, or to unsubscribe from the list, please visit 
>>> http://lists.opencms.org/mailman/listinfo/opencms-dev
>>>
>>>
>>>       
>> _______________________________________________
>> This mail is sent to you from the opencms-dev mailing list To 
>> change your list options, or to unsubscribe from the list, 
>> please visit http://lists.opencms.org/mailman/listinfo/opencms-dev
>>
>>
>>     
>
>
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
>