[Maintain-dev] [JIRA] Closed: (MNT-78) MySQL setup instructions are incomplete

[Michael Clay (JIRA)]

     [ http://bugs.osuosl.org/browse/MNT-78?page=history ]
     
Michael Clay closed MNT-78:
---------------------------

     Resolution: Fixed
    Fix Version: 2.4.0

The 2.4 instructions are much more clear now.  The database config idea will not be implemented this coming release, but the built scripts are more than likely going to get converted.  This would make this kind of idea more in the realm of the possibility, but this issue's primary purpose was to shed light onto documentation, which is fixed.

> MySQL setup instructions are incomplete
> ---------------------------------------
>
>          Key: MNT-78
>          URL: http://bugs.osuosl.org/browse/MNT-78
>      Project: Maintain
>         Type: Bug
>     Versions: 2.2
>  Environment: RHL 9 - plain jane install
>     Reporter: R P Herrold
>     Assignee: Michael Clay
>     Priority: Minor
>      Fix For: 2.4.0

>
>
> A couple of items:
> 1. The instructions at item 1 of 
>     /maintain-2.2.3/INSTALL
> do not prompt the end user to first make the underlying database, nor (one assumes) test for its presence when passed in on the command line.  The first subissue is to somply add an earlier bullet item in the instructions, with the database setup as per the example below.
> [herrold at gateway2000 sql]$ mysql -u root -p maintain < maintain.sql
> Enter password:
> ERROR 1049: Unknown database 'maintain'
> [herrold at gateway2000 sql]$ mysql -u root -p
> Enter password:
> Welcome to the MySQL monitor.  Commands end with ; or \g.
> Your MySQL connection id is 3 to server version: 3.23.58
> Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
> mysql> create database maintain ;
> Query OK, 1 row affected (0.04 sec)
> mysql> quit ;
> Bye
> [herrold at gateway2000 sql]$ mysql -u root -p maintain < maintain.sql
> Enter password:
> [herrold at gateway2000 sql]$
> ---------------------------------------------------------------------
> Item 2, then would be to test if the command line database name passed in exists, and to gracefully carp and die if it is missing
> Item 3 is more general:  The need to migrate and alter schema always exists.  In examining the tablesmysql> show tables
>     -> ;
> +---------------------+
> | Tables_in_maintain  |
> +---------------------+
> | autoreg             |
> | dhcp_options        |
> | domain              |
> | help                |
> | host                |
> | host_history        |
> | ip_blocks           |
> | nameserver          |
> | object_history      |
> | object_option       |
> | pointer             |
> | ranges              |
> | session             |
> | soa                 |
> | staging             |
> | staging_permissions |
> | subnet              |
> | user                |
> | vlan                |
> | workgroup           |
> | zone                |
> | zone_cname          |
> | zone_domain         |
> | zone_mx             |
> | zone_range          |
> | zone_user           |
> | zone_workgroup      |
> +---------------------+
> 27 rows in set (0.00 sec)
> It does not appear that an internal 'configuration' table, to hold name/value text pairs, exists.  By adding such a table, it then may be then be managed and queried by php code and scripting, to determine, say, the preferred email address of the 'abuse adminsistrator', or the database schema version and related information.  
> This in turn permits more intelligent development.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://bugs.osuosl.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira