Mailing-List: contact connectors-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: connectors-dev@incubator.apache.org
Date: Thu, 3 May 2012 19:17:00 -0400 (EDT)
From: confluence@apache.org
To: connectors-commits@incubator.apache.org
Message-ID: <7182338.60840.1336087020021.JavaMail.confluence@thor>
Subject: [CONF] Apache Connectors Framework > Database Configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated

Space: Apache Connectors Framework (https://cwiki.apache.org/confluence/display/CONNECTORS)
Page: Database Configuration (https://cwiki.apache.org/confluence/display/CONNECTORS/Database+Configuration)
Comment: https://cwiki.apache.org/confluence/display/CONNECTORS/Database+Configuration?focusedCommentId=27845743#comment-27845743

Comment added by Gus Heck:
---------------------------------------------------------------------

Thx for the quick reply :) found the property for db name, and added it above. Seems that in the future folks will likely want control over tablespaces, which partition various tables are on and things like that (I'm not a db guru, but it's due to hearing things like that from the DBA's I've come to expect/produce scripts). I'll give it a whirl with the user I defined and see what privs I need to give it (if any) and note that above.

In reply to a comment by Karl Wright:
You can set the database name also via a parameter.  If you create your own user with privs for table creation in the database you want it to use, then running the Initialize, Register, and RegisterConnector/RegisterAuthority/RegisterOutput commands will do the appropriate database and index creation for you.

We in general discourage the idea that you can set up a schema through a SQL script, because individual connectors (which can be registered or deregistered) also own database tables, which they need to create and destroy accordingly.


Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action