sql::translator::parser::sqlite(3pm) [debian man page]

SQL::Translator::Parser::SQLite(3pm)			User Contributed Perl Documentation		      SQL::Translator::Parser::SQLite(3pm)

NAME

       SQL::Translator::Parser::SQLite - parser for SQLite

SYNOPSIS

	 use SQL::Translator;
	 use SQL::Translator::Parser::SQLite;

	 my $translator = SQL::Translator->new;
	 $translator->parser("SQL::Translator::Parser::SQLite");

DESCRIPTION

       This is a grammar for parsing CREATE statements for SQLite as described here:

	   http://www.sqlite.org/lang.html

       CREATE INDEX

       sql-statement ::=
	   CREATE [TEMP | TEMPORARY] [UNIQUE] INDEX index-name
	    ON [database-name .] table-name ( column-name [, column-name]* )
	    [ ON CONFLICT conflict-algorithm ]

       column-name ::=
	   name [ ASC | DESC ]

       CREATE TABLE

       sql-command ::=
	   CREATE [TEMP | TEMPORARY] TABLE table-name (
	       column-def [, column-def]*
	       [, constraint]*
	    )

       sql-command ::=
	   CREATE [TEMP | TEMPORARY] TABLE table-name AS select-statement

       column-def ::=
	   name [type] [[CONSTRAINT name] column-constraint]*

       type ::=
	   typename |
	    typename ( number ) |
	    typename ( number , number )

       column-constraint ::=
	   NOT NULL [ conflict-clause ] |
	   PRIMARY KEY [sort-order] [ conflict-clause ] |
	   UNIQUE [ conflict-clause ] |
	   CHECK ( expr ) [ conflict-clause ] |
	   DEFAULT value

       constraint ::=
	   PRIMARY KEY ( name [, name]* ) [ conflict-clause ]|
	   UNIQUE ( name [, name]* ) [ conflict-clause ] |
	   CHECK ( expr ) [ conflict-clause ]

       conflict-clause ::=
	   ON CONFLICT conflict-algorithm

       CREATE TRIGGER

       sql-statement ::=
	   CREATE [TEMP | TEMPORARY] TRIGGER trigger-name [ BEFORE | AFTER ]
	   database-event ON [database-name .] table-name
	   trigger-action

       sql-statement ::=
	   CREATE [TEMP | TEMPORARY] TRIGGER trigger-name INSTEAD OF
	   database-event ON [database-name .] view-name
	   trigger-action

       database-event ::=
	   DELETE |
	   INSERT |
	   UPDATE |
	   UPDATE OF column-list

       trigger-action ::=
	   [ FOR EACH ROW | FOR EACH STATEMENT ] [ WHEN expression ]
	       BEGIN
		   trigger-step ; [ trigger-step ; ]*
	       END

       trigger-step ::=
	   update-statement | insert-statement |
	   delete-statement | select-statement

       CREATE VIEW

       sql-command ::=
	   CREATE [TEMP | TEMPORARY] VIEW view-name AS select-statement

       ON CONFLICT clause

	   conflict-clause ::=
	   ON CONFLICT conflict-algorithm

	   conflict-algorithm ::=
	   ROLLBACK | ABORT | FAIL | IGNORE | REPLACE

       expression

       expr ::=
	   expr binary-op expr |
	   expr like-op expr |
	   unary-op expr |
	   ( expr ) |
	   column-name |
	   table-name . column-name |
	   database-name . table-name . column-name |
	   literal-value |
	   function-name ( expr-list | * ) |
	   expr (+) |
	   expr ISNULL |
	   expr NOTNULL |
	   expr [NOT] BETWEEN expr AND expr |
	   expr [NOT] IN ( value-list ) |
	   expr [NOT] IN ( select-statement ) |
	   ( select-statement ) |
	   CASE [expr] ( WHEN expr THEN expr )+ [ELSE expr] END

       like-op::=
	   LIKE | GLOB | NOT LIKE | NOT GLOB

AUTHOR

       Ken Youens-Clark <kclark@cpan.org>.

SEE ALSO

       perl(1), Parse::RecDescent, SQL::Translator::Schema.

perl v5.14.2							    2012-01-18				      SQL::Translator::Parser::SQLite(3pm)

Check Out this Related Man Page

CREATE CONSTRAINT 
TRIGGER(7)					   SQL Commands 				      CREATE CONSTRAINT TRIGGER(7)

NAME

       CREATE CONSTRAINT TRIGGER - define a new constraint trigger

SYNOPSIS

       CREATE CONSTRAINT TRIGGER name
	   AFTER event [ OR ... ]
	   ON table_name
	   [ FROM referenced_table_name ]
	   { NOT DEFERRABLE | [ DEFERRABLE ] { INITIALLY IMMEDIATE | INITIALLY DEFERRED } }
	   FOR EACH ROW
	   EXECUTE PROCEDURE funcname ( arguments )

DESCRIPTION

       CREATE  CONSTRAINT TRIGGER creates a constraint trigger. This is the same as a regular trigger except that the timing of the trigger firing
       can be adjusted using SET CONSTRAINTS [set_constraints(7)].  Constraint triggers must be AFTER ROW triggers. They can be  fired	either	at
       the  end of the statement causing the triggering event, or at the end of the containing transaction; in the latter case they are said to be
       deferred. A pending deferred-trigger firing can also be forced to happen immediately by using SET CONSTRAINTS.

PARAMETERS

       name   The name of the constraint trigger. This is also the name to use when modifying the trigger's behavior using SET	CONSTRAINTS.   The
	      name cannot be schema-qualified -- the trigger inherits the schema of its table.

       event  One of INSERT, UPDATE, or DELETE; this specifies the event that will fire the trigger. Multiple events can be specified using OR.

       table_name
	      The (possibly schema-qualified) name of the table in which the triggering events occur.

       referenced_table_name
	      The  (possibly schema-qualified) name of another table referenced by the constraint. This option is used for foreign-key constraints
	      and is not recommended for general use.

       DEFERRABLE

       NOT DEFERRABLE

       INITIALLY IMMEDIATE

       INITIALLY DEFERRED
	      The default timing of the trigger.  See the CREATE TABLE [create_table(7)] documentation for details of these constraint options.

       funcname
	      The function to call when the trigger is fired. See CREATE TRIGGER [create_trigger(7)] for details.

       arguments
	      Optional argument strings to pass to the trigger function. See CREATE TRIGGER [create_trigger(7)] for details.

COMPATIBILITY

       CREATE CONSTRAINT TRIGGER is a PostgreSQL extension of the SQL standard.

SEE ALSO

       CREATE TRIGGER [create_trigger(7)], DROP TRIGGER [drop_trigger(7)], SET CONSTRAINTS [set_constraints(7)]

SQL - Language Statements					    2010-05-14					      CREATE CONSTRAINT TRIGGER(7)

Linux and UNIX Man Pages

sql::translator::parser::sqlite(3pm) [debian man page]

Check Out this Related Man Page