Return-Path: X-Original-To: apmail-openmeetings-user-archive@www.apache.org Delivered-To: apmail-openmeetings-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E48C2ECD2 for ; Sat, 9 Feb 2013 14:56:12 +0000 (UTC) Received: (qmail 71026 invoked by uid 500); 9 Feb 2013 14:56:12 -0000 Delivered-To: apmail-openmeetings-user-archive@openmeetings.apache.org Received: (qmail 70984 invoked by uid 500); 9 Feb 2013 14:56:12 -0000 Mailing-List: contact user-help@openmeetings.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@openmeetings.apache.org Delivered-To: mailing list user@openmeetings.apache.org Received: (qmail 70967 invoked by uid 99); 9 Feb 2013 14:56:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Feb 2013 14:56:11 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of solomax666@gmail.com designates 209.85.160.43 as permitted sender) Received: from [209.85.160.43] (HELO mail-pb0-f43.google.com) (209.85.160.43) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Feb 2013 14:56:06 +0000 Received: by mail-pb0-f43.google.com with SMTP id md12so143815pbc.16 for ; Sat, 09 Feb 2013 06:55:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=E3FK24z/qp0PRto7398K+UcwZ1s9a77mD7XQhWShDD4=; b=igkkk29zcBsZWgS+wKzP/Z1iVt9jL5CaYvpoQlMlSGvTxWh9ddcGkl5FX8Sj70e7Vb NV4A2zFcopuP2C4cQAh5f1F1DRb7CWY/h2Gs/0KXTb3KfCGe8G9iL8fk3/RioaTRxkiT 4UNys08BNn7g9biX2JGz/Y/Rf0bbOvluJMocnh2tR1jDJ6is5h5j5c3mAEq/X1MW09sA KtwRiFQAB6wbA+e1UlqVF8eEZJ1mjD0Vd59th+/dv7ZA4ID1QZJlBOXSZrcxErptz2UP Nw2L58lWvLJno7jTIoQIs/pGjqS+Xv+X0rqVFqWUMZWNiBmMqUucbHKiyhiiVlAyGmvE thXg== MIME-Version: 1.0 X-Received: by 10.66.83.134 with SMTP id q6mr27561139pay.34.1360421746179; Sat, 09 Feb 2013 06:55:46 -0800 (PST) Received: by 10.66.16.72 with HTTP; Sat, 9 Feb 2013 06:55:46 -0800 (PST) In-Reply-To: <36045.92.231.250.47.1360419784.squirrel@webmail.eledia.de> References: <687297651.20130207193829@3bits.es> <55D8E823-095E-443D-AC3A-018DDA7BBC48@robertbird.com.au> <1360312956.75675.YahooMailNeo@web162403.mail.bf1.yahoo.com> <36045.92.231.250.47.1360419784.squirrel@webmail.eledia.de> Date: Sat, 9 Feb 2013 21:55:46 +0700 Message-ID: Subject: Re: Problems with installing OM 2.1 on postgresql From: Maxim Solodovnik To: user Content-Type: multipart/alternative; boundary=f46d042f9494ecff5f04d54bdef9 X-Virus-Checked: Checked by ClamAV on apache.org --f46d042f9494ecff5f04d54bdef9 Content-Type: text/plain; charset=UTF-8 I have changed the table name for the user, to be om_user It should work now. this might be the temporary solution. We double check all databases before release On Sat, Feb 9, 2013 at 9:23 PM, wrote: > Hello, > > I tried to install the latest build of OM 2.1 > (2.1.0.r1444299-09-02-2013_0050) on postgres (9.1) under debian wheezy. > > But the last five tables of the database (user, user_contact, user_data, > user_level, whiteboard) where not created, not by using the red5-script > for init.d nor by using the red5-debug script. > > What do I have to do to finish the installation? > > In general: > Is it possilbe to use postgresql instead of mysql? Or is mysql the > reference-database for OM? > > Thank you for your help! > Michael > > PS: Here are an excerpt of the postgres-log: > 2013-02-09 16:07:24 CET ANWEISUNG: CREATE TABLE user (id BIGSERIAL NOT > NULL, activatehash VARCHAR(255), age TIMESTAMP, availible INTEGER, deleted > BOOL, externalUserId VARCHAR(255), externalUserType VARCHAR(255), > firstname VARCHAR(255), forceTimeZoneCheck BOOL, language_id BIGINT, > lastlogin TIMESTAMP, lastname VARCHAR(255), lasttrans BIGINT, level_id > BIGINT, login VARCHAR(255), password VARCHAR(255), pictureuri > VARCHAR(255), regdate TIMESTAMP, resethash VARCHAR(255), salutations_id > BIGINT, sendSMS BOOL, show_contact_data BOOL, > show_contact_data_to_contacts BOOL, starttime TIMESTAMP, status INTEGER, > updatetime TIMESTAMP, user_offers VARCHAR(255), user_searchs VARCHAR(255), > adresses_id BIGINT, omtimezoneId BIGINT, sip_user_id BIGINT, PRIMARY KEY > (id)) > -- WBR Maxim aka solomax --f46d042f9494ecff5f04d54bdef9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have changed the table name for the user, to be om_user<= div style>It should work now.

this mig= ht be the temporary solution. We double check all databases before release<= /div>


On Sat,= Feb 9, 2013 at 9:23 PM, <michael.wuttke@eledia.de> = wrote:
Hello,

I tried to install the latest build of OM 2.1
(2.1.0.r1444299-09-02-2013_0050) on postgres (9.1) under debian wheezy.

But the last five tables of the database (user, user_contact, user_data, user_level, whiteboard) where not created, not by using the red5-script
for init.d nor by using the red5-debug script.

What do I have to do to finish the installation?

In general:
Is it possilbe to use postgresql instead of mysql? Or is mysql the
reference-database for OM?

Thank you for your help!
Michael

PS: Here are an excerpt of the postgres-log:
2013-02-09 16:07:24 CET ANWEISUNG: =C2=A0CREATE TABLE user (id BIGSERIAL NO= T
NULL, activatehash VARCHAR(255), age TIMESTAMP, availible INTEGER, deleted<= br> BOOL, externalUserId VARCHAR(255), externalUserType VARCHAR(255),
firstname VARCHAR(255), forceTimeZoneCheck BOOL, language_id BIGINT,
lastlogin TIMESTAMP, lastname VARCHAR(255), lasttrans BIGINT, level_id
BIGINT, login VARCHAR(255), password VARCHAR(255), pictureuri
VARCHAR(255), regdate TIMESTAMP, resethash VARCHAR(255), salutations_id
BIGINT, sendSMS BOOL, show_contact_data BOOL,
show_contact_data_to_contacts BOOL, starttime TIMESTAMP, status INTEGER, updatetime TIMESTAMP, user_offers VARCHAR(255), user_searchs VARCHAR(255),<= br> adresses_id BIGINT, omtimezoneId BIGINT, sip_user_id BIGINT, PRIMARY KEY (id))



--
WBR
Maxim= aka solomax
--f46d042f9494ecff5f04d54bdef9--