/ 
Bigtop-0.24
River stage zero No dependents
/ Bigtop::ScriptHelp::Style::Original

NAME

Bigtop::ScriptHelp::Style::Original - handles ASCII art for scripts

SYNOPSIS

use Bigtop::ScriptHelp::Style;

my $style = Bigtop::ScriptHelp::Style->get_style( 'Original' );

# then pass $style to methods of Bigtop::ScriptHelp

DESCRIPTION

See Bigtop::ScriptHelp::Style for a description of what this module must do in general.

METHODS

get_db_layout

This method does not use standard in. Instead, it expects traditional ASCII art. See "ASCII Art" below.

ASCII Art

ASCII art allows you to quickly note relationships between tables with simple characters.

Note well: Since the relationships use punctuation that your shell probably loves, you must surround the art with single quotes.

It is easiest to understand the options by seeing an example. So, suppose we have a four table data model describing a bit of our personnel process:

+-----------+       +----------+
|    job    |<------| position |
+-----------+       +----------+
      ^
      |
+-----------+       +----------+
| job_skill |------>|  skill   |
+-----------+       +----------+

First, you'll be happy to know that bigtop's ASCII art is simpler to draw than the above.

What our data model shows is that each position refers to a job (description), each job could require many skills, and each skill could be associated with many jobs. The last two mean that job and skill share a many-to-many relationship.

Here's how to specify this data model in bigtop ASCII art:

bigtop --new HR 'job<-position job<->skill'

This indicates a foreign key from position to job and an implied table, called job_skill, to hold the many-to-many relationship between job and skill.

The same ASCII art can be used with --new and --add for both bigtop and tentmaker scripts.

There are four art operators:

<->

Many-to-many. A new table will be made with foreign keys to each operand table. Each operand table will have a has_many relationship. Note that your Model backend may not understand these relationships. At the time of this writing only Model GantryDBIxClass did, by luck it happens to be the default.

->

The first table has a foreign key pointing to the second.

<-

The second table has a foreign key pointing to the first. This is really a convenience synonymn for ->, but the tables are put into generated SQL in their overall order of appearance.

-

The two tables have a one-to-one relationship. Each of them will have a foreign key pointing to the other.

COLUMN DEFINITIONS

As of Bigtop 0.23, you may use the syntax below to specify information about the columns in your tables, in addition to the table relationships above.

Note Well: When following the instructions below, never be tempted to use spaces inside column definitions. If you need spaces, colons might work. If not, you'll need to edit the generated bigtop file, just like old times.

Column definitions must be placed inside parnetheses immediatly after the table name and immediately before any table relationship operator. Separate columns with commas. Specify type definitions with colons. Use equals for defaults and leading plus signs for optional fields. For example:

bigtop -n App 'family(name,+phone)<-child(name,birth_day:date)'

By default all columns will have type varchar. If you need something else use a colon, as I did for birth_day. If you type definition needs multiple words use colons instead of spaces.

The phone column in the family table has a leading plus sign, and will therefore be optional on the HTML form.

You can still augment the bigtop file later. Existing tables in the bigtop file will have foreign keys added as specified by relation operators, but you parenthetical column lists will be silently ignored. For example:

bigtop -a docs/app.bigtop '
    anniversary(anniversary:date,gift_pref=money)<-family'

This will add a new table called anniversary with anniversary (a date) and gift_pref columns. The later will have a default value in the database and on HTML forms of 'money.' Finally, a new foreign key will be added to the existing family table pointing to the anniversary table.

FORMAL SUMMARY

Here is the formal syntax for each table definition:

name(COL_DEF[,COL_DEF...])

Where name is a valid SQL table name and COL_DEF is as follows:

[+]col_name[:TYPE_INFO][=default]

Where plus makes the HTML form field for the column optional, col_name is a valid SQL column name, and all defaults are literal (they will be quoted in SQL). If you need more interesting defaults, edit the bigtop file after it is updated. TYPE_INFO is a colon separated list of column declaration words.

Suppose you want this column definition:

state int4 NOT NULL DEFAULT 4,

Say this:

state:int4:NOT:NULL=4

AUTHOR

Phil Crow, <crow.phil@gmail.com>

COPYRIGHT AND LICENSE

Copyright (C) 2007, Phil Crow

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.6 or, at your option, any later version of Perl 5 you may have available.