13.08.2012 Views

ACTIONSCRIPT 3 Developer’s Guide en

ACTIONSCRIPT 3 Developer’s Guide en

ACTIONSCRIPT 3 Developer’s Guide en

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>ACTIONSCRIPT</strong> 3.0 DEVELOPER’S GUIDE<br />

SQL support in local databases<br />

comm<strong>en</strong>t ::= single-line-comm<strong>en</strong>t |<br />

block-comm<strong>en</strong>t<br />

single-line-comm<strong>en</strong>t ::= -- single-line<br />

block-comm<strong>en</strong>t ::= /* multiple-lines or block [*/]<br />

A single-line comm<strong>en</strong>t is indicated by two dashes. A single line comm<strong>en</strong>t only ext<strong>en</strong>ds to the <strong>en</strong>d of the curr<strong>en</strong>t line.<br />

Block comm<strong>en</strong>ts can span any number of lines, or be embedded within a single line. If there is no terminating<br />

delimiter, a block comm<strong>en</strong>t ext<strong>en</strong>ds to the <strong>en</strong>d of the input. This situation is not treated as an error. A new SQL<br />

statem<strong>en</strong>t can begin on a line after a block comm<strong>en</strong>t <strong>en</strong>ds. Block comm<strong>en</strong>ts can be embedded anywhere white space<br />

can occur, including inside expressions, and in the middle of other SQL statem<strong>en</strong>ts. Block comm<strong>en</strong>ts do not nest.<br />

Single-line comm<strong>en</strong>ts inside a block comm<strong>en</strong>t are ignored.<br />

EXPRESSIONS<br />

Expressions are subcommands within other SQL blocks. The following describes the valid syntax for an expression<br />

within a SQL statem<strong>en</strong>t:<br />

expr ::= expr binary-op expr |<br />

expr [NOT] like-op expr [ESCAPE expr] |<br />

unary-op expr |<br />

( expr ) |<br />

column-name |<br />

table-name.column-name |<br />

database-name.table-name.column-name |<br />

literal-value |<br />

parameter |<br />

function-name( expr-list | * ) |<br />

expr ISNULL |<br />

expr NOTNULL |<br />

expr [NOT] BETWEEN expr AND expr |<br />

expr [NOT] IN ( value-list ) |<br />

expr [NOT] IN ( select-statem<strong>en</strong>t ) |<br />

expr [NOT] IN [database-name.] table-name |<br />

[EXISTS] ( select-statem<strong>en</strong>t ) |<br />

CASE [expr] ( WHEN expr THEN expr )+ [ELSE expr] END |<br />

CAST ( expr AS type ) |<br />

expr COLLATE collation-name<br />

like-op ::= LIKE | GLOB<br />

binary-op ::= see Operators<br />

unary-op ::= see Operators<br />

parameter ::= :param-name | @param-name | ?<br />

value-list ::= literal-value [, literal-value]*<br />

literal-value ::= literal-string | literal-number | literal-boolean | literal-blob |<br />

literal-null<br />

literal-string ::= 'string value'<br />

literal-number ::= integer | number<br />

literal-boolean ::= true | false<br />

literal-blob ::= X'string of hexadecimal data'<br />

literal-null ::= NULL<br />

An expression is any combination of values and operators that can be resolved to a single value. Expressions can be<br />

divided into two g<strong>en</strong>eral types, according to whether they resolve to a boolean (true or false) value or whether they<br />

resolve to a non-boolean value.<br />

Last updated 6/6/2012<br />

1106

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!