Create a Processing Database » History » Version 4
Anchi Cheng, 03/04/2011 04:50 PM
1 | 4 | Anchi Cheng | h1. Create a Processing Database for the Project |
---|---|---|---|
2 | 1 | Amber Herold | |
3 | 2 | Amber Herold | * Click on a project name on the webpage `http://your_host/project_1_2/project.php`. This will take you to a new webpage `http://your_host/project_1_2/getproject.php?pId=1`. The number following "pId=" depends on the project id automatically assigned to the project. |
4 | * At the end of the Info table, you should see: |
||
5 | 1 | Amber Herold | |
6 | <pre> |
||
7 | processing db: not set (create processing db) db name ap1 |
||
8 | </pre> |
||
9 | |||
10 | You can create the default numbered style database ap... or give it a new name with the same prefix. If you want to specify a database name that does not use the default prefix, please note that your db user specified in the config.php in project_1_2 needs to have the necessary privileges for that database. You may additionally want to change the value assigned to $DEF_PROCESSING_PREFIX in project_1_2/config.php if you want to use your new prefix all the time. |
||
11 | 2 | Amber Herold | * Enter the processing database name and click "create processing db". |
12 | * The page should refresh and display the linked database like this: |
||
13 | 1 | Amber Herold | |
14 | <pre> |
||
15 | processing db: ap1 |
||
16 | </pre> |
||
17 | |||
18 | See next section on trouble shooting if you get the original page instead. |
||
19 | |||
20 | * *Repeat the above process for all your projects.* |
||
21 | |||
22 | If you want all your processing databases combined in one single database (not recommended, as this becomes large very fast), just use the same name for all your projects. |
||
23 | |||
24 | The above procedure not only creates the database, but also create some of the tables that you need to start processing. |
||
25 | |||
26 | h3. Trouble Shooting |
||
27 | |||
28 | If the 'getproject.php' webpage remains unchanged, your processing database link is not accepted. This is usually |
||
29 | caused by an incorrect setting such as: |
||
30 | # The mysql user does not have the privileges to create the named database. |
||
31 | See Section-5.3 on what you should do. To try it again after your mysql correction, you should repeat Section-5.2 to allow reinitialization from the project_1_2 web page and then try 7.2 again. |
||
32 | # You have accessed an earlier version of project web page after you reinitialized the install table in your existing project database. |
||
33 | The install table in the project database is set to deny further changes once any project web page is accessed. As a result, required table property changes and new table insertion would fail. |
||
34 | Here is how to fix it: |
||
35 | # Repeat Seciont-5.2 to allow reinitialization. |
||
36 | # Try Section-7.2 again. |