/macosx-10.9.5/CPANInternal-140/SQL-Abstract/lib/SQL/ |
H A D | Abstract.pm | 246 # first build the 'SET' part of the sql statement 1357 statement handles and use the DBI interface. So, I set out to 1693 It returns an SQL INSERT statement and a list of bind values. 1707 field names, and adds on an SQL C<RETURNING> statement at the end. 1708 This allows you to return data generated by the insert statement 1709 (such as row IDs) without performing another C<SELECT> statement. 1726 This returns a SQL SELECT statement and associated list of bind values, as 1733 Specification of the 'FROM' part of the statement. 1770 It returns an SQL DELETE statement and list of bind values. 2205 the verbatim SQL is passed as part of the statement [all...] |
/macosx-10.9.5/CPANInternal-140/DBIx-Class/lib/DBIx/Class/Schema/ |
H A D | Versioned.pm | 483 Takes an SQL statement and runs it. Override this if you want to handle errors 489 my ($self, $statement) = @_;
|
/macosx-10.9.5/emacs-92/emacs/lisp/progmodes/ |
H A D | cc-vars.el | 695 (statement-cont) 715 SYNTACTIC-SYMBOL can be statement-cont, brace-list-intro, 753 statement-cont substatement-open statement-case-open 958 ;; *) At the start of a statement or declaration means in more detail: 959 ;; At the closest preceding statement/declaration that starts at boi 961 ;; no such statement within the same block, then back up to the 962 ;; surrounding block or statement, add the appropriate 963 ;; statement-block-intro, defun-block-intro or substatement syntax 989 ;; it's at boi, else at the statement(*) a [all...] |
H A D | cc-styles.el | 63 (c-offsets-alist . ((statement-block-intro . +) 68 (statement-case-open . +) 69 (statement-cont . +) 83 (c-offsets-alist . ((statement-block-intro . +) 88 (statement-cont . +)))) 93 (c-offsets-alist . ((statement-block-intro . +) 98 (statement-cont . +) 105 (c-offsets-alist . ((statement-block-intro . +) 109 (statement-cont . +)))) 125 (block-open . 0) ; Get indentation from `statement' instea [all...] |
/macosx-10.9.5/vim-53/runtime/indent/ |
H A D | mp.vim | 195 " if this is :endgroup statement {{{2
|
H A D | python.vim | 138 " If the previous line was a stop-execution statement...
|
/macosx-10.9.5/vim-53/runtime/syntax/ |
H A D | ibasic.vim | 141 " Used with OPEN statement
|
H A D | msmessages.vim | 87 " Types (used in MessageIdTypedef statement)
|
H A D | natural.vim | 102 " Formats in write statement
|
H A D | rebol.vim | 137 " Debug statement
|
H A D | sqlinformix.vim | 106 syn keyword sqlKeyword statement statistics synonym
|
H A D | basic.vim | 136 " Used with OPEN statement
|
H A D | freebasic.vim | 203 " Used with OPEN statement
|
/macosx-10.9.5/vim-53/runtime/autoload/ |
H A D | phpcomplete.vim | 1379 \ 'db2_exec(': 'resource connection, string statement [, array options] | resource', 1400 \ 'db2_prepare(': 'resource connection, string statement [, array options] | resource', 2844 \ 'mssql_free_statement(': 'resource statement | bool', 3266 \ 'oci_define_by_name(': 'resource statement, string column_name, mixed &variable [, int type] | bool', 3269 \ 'oci_fetch_all(': 'resource statement, array &output [, int skip [, int maxrows [, int flags]]] | int', 3270 \ 'oci_fetch_array(': 'resource statement [, int mode] | array', 3271 \ 'oci_fetch_assoc(': 'resource statement | array', 3272 \ 'oci_fetch(': 'resource statement | bool', 3273 \ 'ocifetchinto(': 'resource statement, array &result [, int mode] | int', 3274 \ 'oci_fetch_object(': 'resource statement | objec [all...] |
H A D | sqlcomplete.vim | 674 " Search backwards to the beginning of the statement 682 " 1. Another select/update/delete statement 762 " Not a SQL statement, do not display a list
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class/lib/DBIx/ |
H A D | Class.pm | 187 resultset is used as an iterator it only fetches rows off the statement
|
/macosx-10.9.5/CPANInternal-140/Log-Log4perl/lib/Log/Log4perl/ |
H A D | Appender.pm | 431 as log messages. If a statement like
|
H A D | Filter.pm | 191 it otherwise. The statement can be negated by saying
|
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/lib/Log/Log4perl/ |
H A D | Filter.pm | 195 it otherwise. The statement can be negated by saying
|
/macosx-10.9.5/ksh-20/ksh/src/cmd/INIT/ |
H A D | mktest.sh | 288 then print -u2 -r -- $command: $SCRIPT: UNIT statement or operand expected
|
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/lib/Log/ |
H A D | Log4perl.pm | 862 level would allow a logger's logging statement to go through, use the 886 low to log the statement anyway, like in: 1086 The Log4perl way is that a logging statement I<should not> 1102 newline to the log statement. This doesn't work well, however, if you, say, 1214 %L Line number within the file where the log statement was issued 1287 encounters a log statement -- no matter if logging is enabled or not. 1345 C<Log::Log4perl> uses I<categories> to determine if a log statement in 2226 statement. So, for example 2338 then a log statement like
|
/macosx-10.9.5/CPANInternal-140/Log-Log4perl/ |
H A D | README | 216 allow a logger's logging statement to go through, use the logger's 237 level is too low to log the statement anyway, like in: 501 %L Line number within the file where the log statement was issued 570 encounters a log statement -- no matter if logging is enabled or not. 623 "Log::Log4perl" uses *categories* to determine if a log statement in a 1400 or die() or exit() statement. So, for example 1509 then a log statement like
|
/macosx-10.9.5/CPANInternal-140/Log-Log4perl/lib/Log/ |
H A D | Log4perl.pm | 710 level would allow a logger's logging statement to go through, use the 733 low to log the statement anyway, like in: 1011 %L Line number within the file where the log statement was issued 1080 encounters a log statement -- no matter if logging is enabled or not. 1136 C<Log::Log4perl> uses I<categories> to determine if a log statement in 1969 statement. So, for example 2081 then a log statement like
|
/macosx-10.9.5/CPANInternal-140/Log-Log4perl-1.40/ |
H A D | README | 223 allow a logger's logging statement to go through, use the logger's 244 level is too low to log the statement anyway, like in: 434 The Log4perl way is that a logging statement *should not* contain a 450 newline to the log statement. This doesn't work well, however, if you, 557 %L Line number within the file where the log statement was issued 630 encounters a log statement -- no matter if logging is enabled or not. 685 uses *categories* to determine if a log statement in a component should 1512 or die() or exit() statement. So, for example 1621 then a log statement like
|
/macosx-10.9.5/CPANInternal-140/DBIx-Class/lib/DBIx/Class/ |
H A D | Schema.pm | 724 if you want to turn on SQL statement debugging at runtime, or set the 1042 to have the SQL produced include a C<DROP TABLE> statement for each table
|