public interface Statement extends Wrapper, AutoCloseable
The object used for executing a static SQL statement and returning the results it produces.
By default, only one ResultSet
object per Statement
object can be open at the same time. Therefore, if the reading of one
ResultSet
object is interleaved
with the reading of another, each must have been generated by
different Statement
objects. All execution methods in the
Statement
interface implicitly close a current
ResultSet
object of the statement if an open one exists.
Connection.createStatement()
,
ResultSet
| Modifier and Type | Field and Description |
|---|---|
static int |
CLOSE_ALL_RESULTS
The constant indicating that all
ResultSet objects that
have previously been kept open should be closed when calling
getMoreResults . |
static int |
CLOSE_CURRENT_RESULT
The constant indicating that the current
ResultSet object
should be closed when calling getMoreResults . |
static int |
EXECUTE_FAILED
The constant indicating that an error occurred while executing a
batch statement.
|
static int |
KEEP_CURRENT_RESULT
The constant indicating that the current
ResultSet object
should not be closed when calling getMoreResults . |
static int |
NO_GENERATED_KEYS
The constant indicating that generated keys should not be made
available for retrieval.
|
static int |
RETURN_GENERATED_KEYS
The constant indicating that generated keys should be made
available for retrieval.
|
static int |
SUCCESS_NO_INFO
The constant indicating that a batch statement executed successfully
but that no count of the number of rows it affected is available.
|
| Modifier and Type | Method and Description |
|---|---|
void |
addBatch(String sql)
Adds the given SQL command to the current list of commands for this
Statement object. |
void |
cancel()
Cancels this
Statement object if both the DBMS and
driver support aborting an SQL statement. |
void |
clearBatch()
Empties this
Statement object's current list of
SQL commands. |
void |
clearWarnings()
Clears all the warnings reported on this
Statement
object. |
void |
close()
Releases this
Statement object's database
and JDBC resources immediately instead of waiting for
this to happen when it is automatically closed. |
void |
closeOnCompletion()
Specifies that this
Statement will be closed when all its
dependent result sets are closed. |
boolean |
execute(String sql)
Executes the given SQL statement, which may return multiple results.
|
boolean |
execute(String sql,
int autoGeneratedKeys)
Executes the given SQL statement, which may return multiple results,
and signals the driver that any
auto-generated keys should be made available
for retrieval.
|
boolean |
execute(String sql,
int[] columnIndexes)
Executes the given SQL statement, which may return multiple results,
and signals the driver that the
auto-generated keys indicated in the given array should be made available
for retrieval.
|
boolean |
execute(String sql,
String[] columnNames)
Executes the given SQL statement, which may return multiple results,
and signals the driver that the
auto-generated keys indicated in the given array should be made available
for retrieval.
|
int[] |
executeBatch()
Submits a batch of commands to the database for execution and
if all commands execute successfully, returns an array of update counts.
|
default long[] |
executeLargeBatch()
Submits a batch of commands to the database for execution and
if all commands execute successfully, returns an array of update counts.
|
default long |
executeLargeUpdate(String sql)
Executes the given SQL statement, which may be an
INSERT ,
UPDATE , or DELETE statement or an
SQL statement that returns nothing, such as an SQL DDL statement. |
default long |
executeLargeUpdate(String sql,
int autoGeneratedKeys)
Executes the given SQL statement and signals the driver with the
given flag about whether the
auto-generated keys produced by this
Statement object
should be made available for retrieval. |
default long |
executeLargeUpdate(String sql,
int[] columnIndexes)
Executes the given SQL statement and signals the driver that the
auto-generated keys indicated in the given array should be made available
for retrieval.
|
default long |
executeLargeUpdate(String sql,
String[] columnNames)
Executes the given SQL statement and signals the driver that the
auto-generated keys indicated in the given array should be made available
for retrieval.
|
ResultSet |
executeQuery(String sql)
Executes the given SQL statement, which returns a single
ResultSet object. |
int |
executeUpdate(String sql)
Executes the given SQL statement, which may be an
INSERT ,
UPDATE , or DELETE statement or an
SQL statement that returns nothing, such as an SQL DDL statement. |
int |
executeUpdate(String sql,
int autoGeneratedKeys)
Executes the given SQL statement and signals the driver with the
given flag about whether the
auto-generated keys produced by this
Statement object
should be made available for retrieval. |
int |
executeUpdate(String sql,
int[] columnIndexes)
Executes the given SQL statement and signals the driver that the
auto-generated keys indicated in the given array should be made available
for retrieval.
|
int |
executeUpdate(String sql,
String[] columnNames)
Executes the given SQL statement and signals the driver that the
auto-generated keys indicated in the given array should be made available
for retrieval.
|
Connection |
getConnection()
Retrieves the
Connection object
that produced this Statement object. |
int |
getFetchDirection()
Retrieves the direction for fetching rows from
database tables that is the default for result sets
generated from this
Statement object. |
int |
getFetchSize()
Retrieves the number of result set rows that is the default
fetch size for
ResultSet objects
generated from this Statement object. |
ResultSet |
getGeneratedKeys()
Retrieves any auto-generated keys created as a result of executing this
Statement object. |
default long |
getLargeMaxRows()
Retrieves the maximum number of rows that a
ResultSet object produced by this
Statement object can contain. |
default long |
getLargeUpdateCount()
Retrieves the current result as an update count; if the result
is a
ResultSet object or there are no more results, -1
is returned. |
int |
getMaxFieldSize()
Retrieves the maximum number of bytes that can be
returned for character and binary column values in a
ResultSet
object produced by this Statement object. |
int |
getMaxRows()
Retrieves the maximum number of rows that a
ResultSet object produced by this
Statement object can contain. |
boolean |
getMoreResults()
Moves to this
Statement object's next result, returns
true if it is a ResultSet object, and
implicitly closes any current ResultSet
object(s) obtained with the method getResultSet . |
boolean |
getMoreResults(int current)
Moves to this
Statement object's next result, deals with
any current ResultSet object(s) according to the instructions
specified by the given flag, and returns
true if the next result is a ResultSet object. |
int |
getQueryTimeout()
Retrieves the number of seconds the driver will
wait for a
Statement object to execute. |
ResultSet |
getResultSet()
Retrieves the current result as a
ResultSet object. |
int |
getResultSetConcurrency()
Retrieves the result set concurrency for
ResultSet objects
generated by this Statement object. |
int |
getResultSetHoldability()
Retrieves the result set holdability for
ResultSet objects
generated by this Statement object. |
int |
getResultSetType()
Retrieves the result set type for
ResultSet objects
generated by this Statement object. |
int |
getUpdateCount()
Retrieves the current result as an update count;
if the result is a
ResultSet object or there are no more results, -1
is returned. |
SQLWarning |
getWarnings()
Retrieves the first warning reported by calls on this
Statement object. |
boolean |
isClosed()
Retrieves whether this
Statement object has been closed. |
boolean |
isCloseOnCompletion()
Returns a value indicating whether this
Statement will be
closed when all its dependent result sets are closed. |
boolean |
isPoolable()
Returns a value indicating whether the
Statement
is poolable or not. |
void |
setCursorName(String name)
Sets the SQL cursor name to the given
String , which
will be used by subsequent Statement object
execute methods. |
void |
setEscapeProcessing(boolean enable)
Sets escape processing on or off.
|
void |
setFetchDirection(int direction)
Gives the driver a hint as to the direction in which
rows will be processed in
ResultSet
objects created using this Statement object. |
void |
setFetchSize(int rows)
Gives the JDBC driver a hint as to the number of rows that should
be fetched from the database when more rows are needed for
ResultSet objects generated by this Statement . |
default void |
setLargeMaxRows(long max)
Sets the limit for the maximum number of rows that any
ResultSet object generated by this Statement
object can contain to the given number. |
void |
setMaxFieldSize(int max)
Sets the limit for the maximum number of bytes that can be returned for
character and binary column values in a
ResultSet
object produced by this Statement object. |
void |
setMaxRows(int max)
Sets the limit for the maximum number of rows that any
ResultSet object generated by this Statement
object can contain to the given number. |
void |
setPoolable(boolean poolable)
Requests that a
Statement be pooled or not pooled. |
void |
setQueryTimeout(int seconds)
Sets the number of seconds the driver will wait for a
Statement object to execute to the given number of seconds. |
isWrapperFor, unwrap
static final int CLOSE_CURRENT_RESULT
ResultSet
object
should be closed when calling getMoreResults
.static final int KEEP_CURRENT_RESULT
ResultSet
object
should not be closed when calling getMoreResults
.static final int CLOSE_ALL_RESULTS
ResultSet
objects that
have previously been kept open should be closed when calling
getMoreResults
.static final int SUCCESS_NO_INFO
static final int EXECUTE_FAILED
static final int RETURN_GENERATED_KEYS
static final int NO_GENERATED_KEYS
ResultSet executeQuery(String sql) throws SQLException
ResultSet
object.
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
sql
- an SQL statement to be sent to the database, typically a
static SQL SELECT
statementResultSet
object that contains the data produced
by the given query; never null
SQLException
- if a database access error occurs,
this method is called on a closed Statement
, the given
SQL statement produces anything other than a single
ResultSet
object, the method is called on a
PreparedStatement
or CallableStatement
SQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
int executeUpdate(String sql) throws SQLException
INSERT
,
UPDATE
, or DELETE
statement or an
SQL statement that returns nothing, such as an SQL DDL statement.
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
sql
- an SQL Data Manipulation Language (DML) statement, such as INSERT
, UPDATE
or
DELETE
; or an SQL statement that returns nothing,
such as a DDL statement.SQLException
- if a database access error occurs,
this method is called on a closed Statement
, the given
SQL statement produces a ResultSet
object, the method is called on a
PreparedStatement
or CallableStatement
SQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
void close() throws SQLException
Statement
object's database
and JDBC resources immediately instead of waiting for
this to happen when it is automatically closed.
It is generally good practice to release resources as soon as
you are finished with them to avoid tying up database
resources.
Calling the method close
on a Statement
object that is already closed has no effect.
Note:When a Statement
object is
closed, its current ResultSet
object, if one exists, is
also closed.
close
in interface AutoCloseable
SQLException
- if a database access error occursint getMaxFieldSize() throws SQLException
ResultSet
object produced by this Statement
object.
This limit applies only to BINARY
, VARBINARY
,
LONGVARBINARY
, CHAR
, VARCHAR
,
NCHAR
, NVARCHAR
, LONGNVARCHAR
and LONGVARCHAR
columns. If the limit is exceeded, the
excess data is silently discarded.SQLException
- if a database access error occurs or
this method is called on a closed Statement
setMaxFieldSize(int)
void setMaxFieldSize(int max) throws SQLException
ResultSet
object produced by this Statement
object.
This limit applies
only to BINARY
, VARBINARY
,
LONGVARBINARY
, CHAR
, VARCHAR
,
NCHAR
, NVARCHAR
, LONGNVARCHAR
and
LONGVARCHAR
fields. If the limit is exceeded, the excess data
is silently discarded. For maximum portability, use values
greater than 256.max
- the new column size limit in bytes; zero means there is no limitSQLException
- if a database access error occurs,
this method is called on a closed Statement
or the condition max >= 0
is not satisfiedgetMaxFieldSize()
int getMaxRows() throws SQLException
ResultSet
object produced by this
Statement
object can contain. If this limit is exceeded,
the excess rows are silently dropped.ResultSet
object produced by this Statement
object;
zero means there is no limitSQLException
- if a database access error occurs or
this method is called on a closed Statement
setMaxRows(int)
void setMaxRows(int max) throws SQLException
ResultSet
object generated by this Statement
object can contain to the given number.
If the limit is exceeded, the excess
rows are silently dropped.max
- the new max rows limit; zero means there is no limitSQLException
- if a database access error occurs,
this method is called on a closed Statement
or the condition max >= 0
is not satisfiedgetMaxRows()
void setEscapeProcessing(boolean enable) throws SQLException
The Connection
and DataSource
property
escapeProcessing
may be used to change the default escape processing
behavior. A value of true (the default) enables escape Processing for
all Statement
objects. A value of false disables escape processing
for all Statement
objects. The setEscapeProcessing
method may be used to specify the escape processing behavior for an
individual Statement
object.
Note: Since prepared statements have usually been parsed prior
to making this call, disabling escape processing for
PreparedStatements
objects will have no effect.
enable
- true
to enable escape processing;
false
to disable itSQLException
- if a database access error occurs or
this method is called on a closed Statement
int getQueryTimeout() throws SQLException
Statement
object to execute.
If the limit is exceeded, a
SQLException
is thrown.SQLException
- if a database access error occurs or
this method is called on a closed Statement
setQueryTimeout(int)
void setQueryTimeout(int seconds) throws SQLException
Statement
object to execute to the given number of seconds.
By default there is no limit on the amount of time allowed for a running
statement to complete. If the limit is exceeded, an
SQLTimeoutException
is thrown.
A JDBC driver must apply this limit to the execute
,
executeQuery
and executeUpdate
methods.
Note: JDBC driver implementations may also apply this
limit to ResultSet
methods
(consult your driver vendor documentation for details).
Note: In the case of Statement
batching, it is
implementation defined as to whether the time-out is applied to
individual SQL commands added via the addBatch
method or to
the entire batch of SQL commands invoked by the executeBatch
method (consult your driver vendor documentation for details).
seconds
- the new query timeout limit in seconds; zero means
there is no limitSQLException
- if a database access error occurs,
this method is called on a closed Statement
or the condition seconds >= 0
is not satisfiedgetQueryTimeout()
void cancel() throws SQLException
Statement
object if both the DBMS and
driver support aborting an SQL statement.
This method can be used by one thread to cancel a statement that
is being executed by another thread.SQLException
- if a database access error occurs or
this method is called on a closed Statement
SQLFeatureNotSupportedException
- if the JDBC driver does not support
this methodSQLWarning getWarnings() throws SQLException
Statement
object.
Subsequent Statement
object warnings will be chained to this
SQLWarning
object.
The warning chain is automatically cleared each time
a statement is (re)executed. This method may not be called on a closed
Statement
object; doing so will cause an SQLException
to be thrown.
Note: If you are processing a ResultSet
object, any
warnings associated with reads on that ResultSet
object
will be chained on it rather than on the Statement
object that produced it.
SQLWarning
object or null
if there are no warningsSQLException
- if a database access error occurs or
this method is called on a closed Statement
void clearWarnings() throws SQLException
Statement
object. After a call to this method,
the method getWarnings
will return
null
until a new warning is reported for this
Statement
object.SQLException
- if a database access error occurs or
this method is called on a closed Statement
void setCursorName(String name) throws SQLException
String
, which
will be used by subsequent Statement
object
execute
methods. This name can then be
used in SQL positioned update or delete statements to identify the
current row in the ResultSet
object generated by this
statement. If the database does not support positioned update/delete,
this method is a noop. To insure that a cursor has the proper isolation
level to support updates, the cursor's SELECT
statement
should have the form SELECT FOR UPDATE
. If
FOR UPDATE
is not present, positioned updates may fail.
Note: By definition, the execution of positioned updates and
deletes must be done by a different Statement
object than
the one that generated the ResultSet
object being used for
positioning. Also, cursor names must be unique within a connection.
name
- the new cursor name, which must be unique within
a connectionSQLException
- if a database access error occurs or
this method is called on a closed Statement
SQLFeatureNotSupportedException
- if the JDBC driver does not support this methodboolean execute(String sql) throws SQLException
The execute
method executes an SQL statement and indicates the
form of the first result. You must then use the methods
getResultSet
or getUpdateCount
to retrieve the result, and getMoreResults
to
move to any subsequent result(s).
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
sql
- any SQL statementtrue
if the first result is a ResultSet
object; false
if it is an update count or there are
no resultsSQLException
- if a database access error occurs,
this method is called on a closed Statement
,
the method is called on a
PreparedStatement
or CallableStatement
SQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
getResultSet()
,
getUpdateCount()
,
getMoreResults()
ResultSet getResultSet() throws SQLException
ResultSet
object.
This method should be called only once per result.ResultSet
object or
null
if the result is an update count or there are no more resultsSQLException
- if a database access error occurs or
this method is called on a closed Statement
execute(java.lang.String)
int getUpdateCount() throws SQLException
ResultSet
object or there are no more results, -1
is returned. This method should be called only once per result.ResultSet
object or there are no more resultsSQLException
- if a database access error occurs or
this method is called on a closed Statement
execute(java.lang.String)
boolean getMoreResults() throws SQLException
Statement
object's next result, returns
true
if it is a ResultSet
object, and
implicitly closes any current ResultSet
object(s) obtained with the method getResultSet
.
There are no more results when the following is true:
// stmt is a Statement object
((stmt.getMoreResults() == false) && (stmt.getUpdateCount() == -1))
true
if the next result is a ResultSet
object; false
if it is an update count or there are
no more resultsSQLException
- if a database access error occurs or
this method is called on a closed Statement
execute(java.lang.String)
void setFetchDirection(int direction) throws SQLException
ResultSet
objects created using this Statement
object. The
default value is ResultSet.FETCH_FORWARD
.
Note that this method sets the default fetch direction for
result sets generated by this Statement
object.
Each result set has its own methods for getting and setting
its own fetch direction.
direction
- the initial direction for processing rowsSQLException
- if a database access error occurs,
this method is called on a closed Statement
or the given direction
is not one of ResultSet.FETCH_FORWARD
,
ResultSet.FETCH_REVERSE
, or ResultSet.FETCH_UNKNOWN
getFetchDirection()
int getFetchDirection() throws SQLException
Statement
object.
If this Statement
object has not set
a fetch direction by calling the method setFetchDirection
,
the return value is implementation-specific.Statement
objectSQLException
- if a database access error occurs or
this method is called on a closed Statement
setFetchDirection(int)
void setFetchSize(int rows) throws SQLException
ResultSet
objects generated by this Statement
.
If the value specified is zero, then the hint is ignored.
The default value is zero.rows
- the number of rows to fetchSQLException
- if a database access error occurs,
this method is called on a closed Statement
or the
condition rows >= 0
is not satisfied.getFetchSize()
int getFetchSize() throws SQLException
ResultSet
objects
generated from this Statement
object.
If this Statement
object has not set
a fetch size by calling the method setFetchSize
,
the return value is implementation-specific.Statement
objectSQLException
- if a database access error occurs or
this method is called on a closed Statement
setFetchSize(int)
int getResultSetConcurrency() throws SQLException
ResultSet
objects
generated by this Statement
object.ResultSet.CONCUR_READ_ONLY
or
ResultSet.CONCUR_UPDATABLE
SQLException
- if a database access error occurs or
this method is called on a closed Statement
int getResultSetType() throws SQLException
ResultSet
objects
generated by this Statement
object.ResultSet.TYPE_FORWARD_ONLY
,
ResultSet.TYPE_SCROLL_INSENSITIVE
, or
ResultSet.TYPE_SCROLL_SENSITIVE
SQLException
- if a database access error occurs or
this method is called on a closed Statement
void addBatch(String sql) throws SQLException
Statement
object. The commands in this list can be
executed as a batch by calling the method executeBatch
.
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
sql
- typically this is a SQL INSERT
or
UPDATE
statementSQLException
- if a database access error occurs,
this method is called on a closed Statement
, the
driver does not support batch updates, the method is called on a
PreparedStatement
or CallableStatement
executeBatch()
,
DatabaseMetaData.supportsBatchUpdates()
void clearBatch() throws SQLException
Statement
object's current list of
SQL commands.
SQLException
- if a database access error occurs,
this method is called on a closed Statement
or the
driver does not support batch updatesaddBatch(java.lang.String)
,
DatabaseMetaData.supportsBatchUpdates()
int[] executeBatch() throws SQLException
int
elements of the array that is returned are ordered
to correspond to the commands in the batch, which are ordered
according to the order in which they were added to the batch.
The elements in the array returned by the method executeBatch
may be one of the following:
SUCCESS_NO_INFO
-- indicates that the command was
processed successfully but that the number of rows affected is
unknown
If one of the commands in a batch update fails to execute properly,
this method throws a BatchUpdateException
, and a JDBC
driver may or may not continue to process the remaining commands in
the batch. However, the driver's behavior must be consistent with a
particular DBMS, either always continuing to process commands or never
continuing to process commands. If the driver continues processing
after a failure, the array returned by the method
BatchUpdateException.getUpdateCounts
will contain as many elements as there are commands in the batch, and
at least one of the elements will be the following:
EXECUTE_FAILED
-- indicates that the command failed
to execute successfully and occurs only if a driver continues to
process commands after a command fails
The possible implementations and return values have been modified in
the Java 2 SDK, Standard Edition, version 1.3 to
accommodate the option of continuing to process commands in a batch
update after a BatchUpdateException
object has been thrown.
SQLException
- if a database access error occurs,
this method is called on a closed Statement
or the
driver does not support batch statements. Throws BatchUpdateException
(a subclass of SQLException
) if one of the commands sent to the
database fails to execute properly or attempts to return a result set.SQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
addBatch(java.lang.String)
,
DatabaseMetaData.supportsBatchUpdates()
Connection getConnection() throws SQLException
Connection
object
that produced this Statement
object.SQLException
- if a database access error occurs or
this method is called on a closed Statement
boolean getMoreResults(int current) throws SQLException
Statement
object's next result, deals with
any current ResultSet
object(s) according to the instructions
specified by the given flag, and returns
true
if the next result is a ResultSet
object.
There are no more results when the following is true:
// stmt is a Statement object
((stmt.getMoreResults(current) == false) && (stmt.getUpdateCount() == -1))
current
- one of the following Statement
constants indicating what should happen to current
ResultSet
objects obtained using the method
getResultSet
:
Statement.CLOSE_CURRENT_RESULT
,
Statement.KEEP_CURRENT_RESULT
, or
Statement.CLOSE_ALL_RESULTS
true
if the next result is a ResultSet
object; false
if it is an update count or there are no
more resultsSQLException
- if a database access error occurs,
this method is called on a closed Statement
or the argument
supplied is not one of the following:
Statement.CLOSE_CURRENT_RESULT
,
Statement.KEEP_CURRENT_RESULT
or
Statement.CLOSE_ALL_RESULTS
SQLFeatureNotSupportedException
- if
DatabaseMetaData.supportsMultipleOpenResults
returns
false
and either
Statement.KEEP_CURRENT_RESULT
or
Statement.CLOSE_ALL_RESULTS
are supplied as
the argument.execute(java.lang.String)
ResultSet getGeneratedKeys() throws SQLException
Statement
object. If this Statement
object did
not generate any keys, an empty ResultSet
object is returned.
Note:If the columns which represent the auto-generated keys were not specified, the JDBC driver implementation will determine the columns which best represent the auto-generated keys.
ResultSet
object containing the auto-generated key(s)
generated by the execution of this Statement
objectSQLException
- if a database access error occurs or
this method is called on a closed Statement
SQLFeatureNotSupportedException
- if the JDBC driver does not support this methodint executeUpdate(String sql, int autoGeneratedKeys) throws SQLException
Statement
object
should be made available for retrieval. The driver will ignore the
flag if the SQL statement
is not an INSERT
statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
sql
- an SQL Data Manipulation Language (DML) statement, such as INSERT
, UPDATE
or
DELETE
; or an SQL statement that returns nothing,
such as a DDL statement.autoGeneratedKeys
- a flag indicating whether auto-generated keys
should be made available for retrieval;
one of the following constants:
Statement.RETURN_GENERATED_KEYS
Statement.NO_GENERATED_KEYS
SQLException
- if a database access error occurs,
this method is called on a closed Statement
, the given
SQL statement returns a ResultSet
object,
the given constant is not one of those allowed, the method is called on a
PreparedStatement
or CallableStatement
SQLFeatureNotSupportedException
- if the JDBC driver does not support
this method with a constant of Statement.RETURN_GENERATED_KEYSSQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
int executeUpdate(String sql, int[] columnIndexes) throws SQLException
INSERT
statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
sql
- an SQL Data Manipulation Language (DML) statement, such as INSERT
, UPDATE
or
DELETE
; or an SQL statement that returns nothing,
such as a DDL statement.columnIndexes
- an array of column indexes indicating the columns
that should be returned from the inserted rowSQLException
- if a database access error occurs,
this method is called on a closed Statement
, the SQL
statement returns a ResultSet
object,the second argument
supplied to this method is not an
int
array whose elements are valid column indexes, the method is called on a
PreparedStatement
or CallableStatement
SQLFeatureNotSupportedException
- if the JDBC driver does not support this methodSQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
int executeUpdate(String sql, String[] columnNames) throws SQLException
INSERT
statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
sql
- an SQL Data Manipulation Language (DML) statement, such as INSERT
, UPDATE
or
DELETE
; or an SQL statement that returns nothing,
such as a DDL statement.columnNames
- an array of the names of the columns that should be
returned from the inserted rowINSERT
, UPDATE
,
or DELETE
statements, or 0 for SQL statements
that return nothingSQLException
- if a database access error occurs,
this method is called on a closed Statement
, the SQL
statement returns a ResultSet
object, the
second argument supplied to this method is not a String
array
whose elements are valid column names, the method is called on a
PreparedStatement
or CallableStatement
SQLFeatureNotSupportedException
- if the JDBC driver does not support this methodSQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
boolean execute(String sql, int autoGeneratedKeys) throws SQLException
INSERT
statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
In some (uncommon) situations, a single SQL statement may return multiple result sets and/or update counts. Normally you can ignore this unless you are (1) executing a stored procedure that you know may return multiple results or (2) you are dynamically executing an unknown SQL string.
The execute
method executes an SQL statement and indicates the
form of the first result. You must then use the methods
getResultSet
or getUpdateCount
to retrieve the result, and getMoreResults
to
move to any subsequent result(s).
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
sql
- any SQL statementautoGeneratedKeys
- a constant indicating whether auto-generated
keys should be made available for retrieval using the method
getGeneratedKeys
; one of the following constants:
Statement.RETURN_GENERATED_KEYS
or
Statement.NO_GENERATED_KEYS
true
if the first result is a ResultSet
object; false
if it is an update count or there are
no resultsSQLException
- if a database access error occurs,
this method is called on a closed Statement
, the second
parameter supplied to this method is not
Statement.RETURN_GENERATED_KEYS
or
Statement.NO_GENERATED_KEYS
,
the method is called on a
PreparedStatement
or CallableStatement
SQLFeatureNotSupportedException
- if the JDBC driver does not support
this method with a constant of Statement.RETURN_GENERATED_KEYSSQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
getResultSet()
,
getUpdateCount()
,
getMoreResults()
,
getGeneratedKeys()
boolean execute(String sql, int[] columnIndexes) throws SQLException
INSERT
statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
Under some (uncommon) situations, a single SQL statement may return multiple result sets and/or update counts. Normally you can ignore this unless you are (1) executing a stored procedure that you know may return multiple results or (2) you are dynamically executing an unknown SQL string.
The execute
method executes an SQL statement and indicates the
form of the first result. You must then use the methods
getResultSet
or getUpdateCount
to retrieve the result, and getMoreResults
to
move to any subsequent result(s).
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
sql
- any SQL statementcolumnIndexes
- an array of the indexes of the columns in the
inserted row that should be made available for retrieval by a
call to the method getGeneratedKeys
true
if the first result is a ResultSet
object; false
if it is an update count or there
are no resultsSQLException
- if a database access error occurs,
this method is called on a closed Statement
, the
elements in the int
array passed to this method
are not valid column indexes, the method is called on a
PreparedStatement
or CallableStatement
SQLFeatureNotSupportedException
- if the JDBC driver does not support this methodSQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
getResultSet()
,
getUpdateCount()
,
getMoreResults()
boolean execute(String sql, String[] columnNames) throws SQLException
INSERT
statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
In some (uncommon) situations, a single SQL statement may return multiple result sets and/or update counts. Normally you can ignore this unless you are (1) executing a stored procedure that you know may return multiple results or (2) you are dynamically executing an unknown SQL string.
The execute
method executes an SQL statement and indicates the
form of the first result. You must then use the methods
getResultSet
or getUpdateCount
to retrieve the result, and getMoreResults
to
move to any subsequent result(s).
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
sql
- any SQL statementcolumnNames
- an array of the names of the columns in the inserted
row that should be made available for retrieval by a call to the
method getGeneratedKeys
true
if the next result is a ResultSet
object; false
if it is an update count or there
are no more resultsSQLException
- if a database access error occurs,
this method is called on a closed Statement
,the
elements of the String
array passed to this
method are not valid column names, the method is called on a
PreparedStatement
or CallableStatement
SQLFeatureNotSupportedException
- if the JDBC driver does not support this methodSQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
getResultSet()
,
getUpdateCount()
,
getMoreResults()
,
getGeneratedKeys()
int getResultSetHoldability() throws SQLException
ResultSet
objects
generated by this Statement
object.ResultSet.HOLD_CURSORS_OVER_COMMIT
or
ResultSet.CLOSE_CURSORS_AT_COMMIT
SQLException
- if a database access error occurs or
this method is called on a closed Statement
boolean isClosed() throws SQLException
Statement
object has been closed. A Statement
is closed if the
method close has been called on it, or if it is automatically closed.Statement
object is closed; false if it is still openSQLException
- if a database access error occursvoid setPoolable(boolean poolable) throws SQLException
Statement
be pooled or not pooled. The value
specified is a hint to the statement pool implementation indicating
whether the application wants the statement to be pooled. It is up to
the statement pool manager as to whether the hint is used.
The poolable value of a statement is applicable to both internal statement caches implemented by the driver and external statement caches implemented by application servers and other applications.
By default, a Statement
is not poolable when created, and
a PreparedStatement
and CallableStatement
are poolable when created.
poolable
- requests that the statement be pooled if true and
that the statement not be pooled if false
SQLException
- if this method is called on a closed
Statement
boolean isPoolable() throws SQLException
Statement
is poolable or not.
true
if the Statement
is poolable; false
otherwise
SQLException
- if this method is called on a closed
Statement
setPoolable(boolean)
void closeOnCompletion() throws SQLException
Statement
will be closed when all its
dependent result sets are closed. If execution of the Statement
does not produce any result sets, this method has no effect.
Note: Multiple calls to closeOnCompletion
do
not toggle the effect on this Statement
. However, a call to
closeOnCompletion
does effect both the subsequent execution of
statements, and statements that currently have open, dependent,
result sets.
SQLException
- if this method is called on a closed
Statement
boolean isCloseOnCompletion() throws SQLException
Statement
will be
closed when all its dependent result sets are closed.true
if the Statement
will be closed when all
of its dependent result sets are closed; false
otherwiseSQLException
- if this method is called on a closed
Statement
default long getLargeUpdateCount() throws SQLException
ResultSet
object or there are no more results, -1
is returned. This method should be called only once per result.
This method should be used when the returned row count may exceed
Integer.MAX_VALUE
.
The default implementation will throw UnsupportedOperationException
ResultSet
object or there are no more resultsSQLException
- if a database access error occurs or
this method is called on a closed Statement
execute(java.lang.String)
default void setLargeMaxRows(long max) throws SQLException
ResultSet
object generated by this Statement
object can contain to the given number.
If the limit is exceeded, the excess
rows are silently dropped.
This method should be used when the row limit may exceed
Integer.MAX_VALUE
.
The default implementation will throw UnsupportedOperationException
max
- the new max rows limit; zero means there is no limitSQLException
- if a database access error occurs,
this method is called on a closed Statement
or the condition max >= 0
is not satisfiedgetMaxRows()
default long getLargeMaxRows() throws SQLException
ResultSet
object produced by this
Statement
object can contain. If this limit is exceeded,
the excess rows are silently dropped.
This method should be used when the returned row limit may exceed
Integer.MAX_VALUE
.
The default implementation will return 0
ResultSet
object produced by this Statement
object;
zero means there is no limitSQLException
- if a database access error occurs or
this method is called on a closed Statement
setMaxRows(int)
default long[] executeLargeBatch() throws SQLException
long
elements of the array that is returned are ordered
to correspond to the commands in the batch, which are ordered
according to the order in which they were added to the batch.
The elements in the array returned by the method executeLargeBatch
may be one of the following:
SUCCESS_NO_INFO
-- indicates that the command was
processed successfully but that the number of rows affected is
unknown
If one of the commands in a batch update fails to execute properly,
this method throws a BatchUpdateException
, and a JDBC
driver may or may not continue to process the remaining commands in
the batch. However, the driver's behavior must be consistent with a
particular DBMS, either always continuing to process commands or never
continuing to process commands. If the driver continues processing
after a failure, the array returned by the method
BatchUpdateException.getLargeUpdateCounts
will contain as many elements as there are commands in the batch, and
at least one of the elements will be the following:
EXECUTE_FAILED
-- indicates that the command failed
to execute successfully and occurs only if a driver continues to
process commands after a command fails
This method should be used when the returned row count may exceed
Integer.MAX_VALUE
.
The default implementation will throw UnsupportedOperationException
SQLException
- if a database access error occurs,
this method is called on a closed Statement
or the
driver does not support batch statements. Throws BatchUpdateException
(a subclass of SQLException
) if one of the commands sent to the
database fails to execute properly or attempts to return a result set.SQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
addBatch(java.lang.String)
,
DatabaseMetaData.supportsBatchUpdates()
default long executeLargeUpdate(String sql) throws SQLException
INSERT
,
UPDATE
, or DELETE
statement or an
SQL statement that returns nothing, such as an SQL DDL statement.
This method should be used when the returned row count may exceed
Integer.MAX_VALUE
.
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
The default implementation will throw UnsupportedOperationException
sql
- an SQL Data Manipulation Language (DML) statement,
such as INSERT
, UPDATE
or
DELETE
; or an SQL statement that returns nothing,
such as a DDL statement.SQLException
- if a database access error occurs,
this method is called on a closed Statement
, the given
SQL statement produces a ResultSet
object, the method is called on a
PreparedStatement
or CallableStatement
SQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
default long executeLargeUpdate(String sql, int autoGeneratedKeys) throws SQLException
Statement
object
should be made available for retrieval. The driver will ignore the
flag if the SQL statement
is not an INSERT
statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
This method should be used when the returned row count may exceed
Integer.MAX_VALUE
.
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
The default implementation will throw SQLFeatureNotSupportedException
sql
- an SQL Data Manipulation Language (DML) statement,
such as INSERT
, UPDATE
or
DELETE
; or an SQL statement that returns nothing,
such as a DDL statement.autoGeneratedKeys
- a flag indicating whether auto-generated keys
should be made available for retrieval;
one of the following constants:
Statement.RETURN_GENERATED_KEYS
Statement.NO_GENERATED_KEYS
SQLException
- if a database access error occurs,
this method is called on a closed Statement
, the given
SQL statement returns a ResultSet
object,
the given constant is not one of those allowed, the method is called on a
PreparedStatement
or CallableStatement
SQLFeatureNotSupportedException
- if the JDBC driver does not support
this method with a constant of Statement.RETURN_GENERATED_KEYSSQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
default long executeLargeUpdate(String sql, int[] columnIndexes) throws SQLException
INSERT
statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
This method should be used when the returned row count may exceed
Integer.MAX_VALUE
.
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
The default implementation will throw SQLFeatureNotSupportedException
sql
- an SQL Data Manipulation Language (DML) statement,
such as INSERT
, UPDATE
or
DELETE
; or an SQL statement that returns nothing,
such as a DDL statement.columnIndexes
- an array of column indexes indicating the columns
that should be returned from the inserted rowSQLException
- if a database access error occurs,
this method is called on a closed Statement
, the SQL
statement returns a ResultSet
object,the second argument
supplied to this method is not an
int
array whose elements are valid column indexes, the method is called on a
PreparedStatement
or CallableStatement
SQLFeatureNotSupportedException
- if the JDBC driver does not support this methodSQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
default long executeLargeUpdate(String sql, String[] columnNames) throws SQLException
INSERT
statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
This method should be used when the returned row count may exceed
Integer.MAX_VALUE
.
Note:This method cannot be called on a
PreparedStatement
or CallableStatement
.
The default implementation will throw SQLFeatureNotSupportedException
sql
- an SQL Data Manipulation Language (DML) statement,
such as INSERT
, UPDATE
or
DELETE
; or an SQL statement that returns nothing,
such as a DDL statement.columnNames
- an array of the names of the columns that should be
returned from the inserted rowINSERT
, UPDATE
,
or DELETE
statements, or 0 for SQL statements
that return nothingSQLException
- if a database access error occurs,
this method is called on a closed Statement
, the SQL
statement returns a ResultSet
object, the
second argument supplied to this method is not a String
array
whose elements are valid column names, the method is called on a
PreparedStatement
or CallableStatement
SQLFeatureNotSupportedException
- if the JDBC driver does not support this methodSQLTimeoutException
- when the driver has determined that the
timeout value that was specified by the setQueryTimeout
method has been exceeded and has at least attempted to cancel
the currently running Statement
Dracula Javadoc Sample, Made with Allan Im.


My long term goal is to have agency and stability in my career - through web development I hope to join an industry where I will readily be able to find work and develop enough financial security that in the future whatever path I find myself wanting to take, I have something of a safety net.
Discipline, plain and simple. All human skills are valuable, but the ability to motivate and organise (primarily myself, although these skills in the context of leadership would also be fabulous) is what I am prioritising working on at this point in my life.
I am kind, helpful, and empathetic, I am driven to achieve on an exceptional level, I can communicate effectively, I stand up for what I think is right and good, I work with precision and attention to detail, I have strong analytical capabilities and I love to learn new things. I am easily scared away from my goals by anxiety around completeing them - a flipside of being driven to be perceived by others in a positive light.
The main way I will address my biggest limitation is to work in the behaviour change method of BJ Fogg; trigger-motivation-reward. I have a prescription of SSRIs for my anxiety and depression, but often the battle begins in bed before I can even take them. Getting up is something I have always struggled with, but I've recently been implementing smaller and smaller steps until I can always find the motivation to do the next one. For example, wake up to alarm is a trigger behaviour for the habitual behaviour i want to form: sit upright. And then sit upright is the trigger for stand up out of bed. and then that goes to get breakfast etc etc. I will use this method to build up all the habits I need to, essentially, make productivity and work a habit. The sorts of habits I will look to form would include things like: regularly posting in the slack, communicating immediately whenever my expected timeframe on work is altered,
I feel confident that I've already done quite well at this: posting a request for help with an issue both in the foundations channel (with my direct peers) and my facilitator as soon as it was consistently impeding my progress in a way I could not move forward from. So basically, the EDA slack is my friend for seeking help, advice and support.
Probably pretty similar to what they expect from me: Turn up when agreed/promised, bring a warm attitude to building the space and community (don't be a stranger). I guess they should also be there for support when reached out to, and while obviously they can't be expected to be able to do anything instantly, they should ideally reply by the next working day to confirm that they received my call for support and have considered what they are able to do to help.
I do not have specific immovable scheduling commitments. I am very fortunate for this, and will be generous and sensitive to others who may.


KaarPux
Linux build from source
About
Get Help
Documentation
404: Page not found
Sorry, but
KaarPux
could not find this page...
Please see
About KaarPux
List of all pages


An image from Globant Labs
A video from Globant Labs
A song from Globant Labs
Multimedia files from Globant Labs


| Package | Description |
|---|---|
| com.cyc |
Cyc API factories and constants.
|
| com.cyc.kb |
Interfaces for manipulating CycL-based java objects, both for the purpose of
making assertions and for retrieving terms and values via simple queries.
|
| com.cyc.kb.spi |
All KB API service provider interfaces.
|
| com.cyc.kb.wrapper |
Abstract classes for implementing KbObjects per the decorator pattern.
|
| com.cyc.query |
Interfaces for asking arbitrarily complex queries of a Cyc server, and processing the answers.
|
| Modifier and Type | Field and Description |
|---|---|
static Variable |
Cyc.Constants.ARG
CycL variable ?ARG
|
static Variable |
Cyc.Constants.ARG0
CycL variable ?ARG0
|
static Variable |
Cyc.Constants.ARG1
CycL variable ?ARG1
|
static Variable |
Cyc.Constants.ARG2
CycL variable ?ARG2
|
static Variable |
Cyc.Constants.ARG3
CycL variable ?ARG3
|
static Variable |
Cyc.Constants.ARG4
CycL variable ?ARG4
|
static Variable |
Cyc.Constants.ARG5
CycL variable ?ARG5
|
static Variable |
Cyc.Constants.ARG6
CycL variable ?ARG6
|
static Variable |
Cyc.Constants.ARG7
CycL variable ?ARG7
|
static Variable |
Cyc.Constants.ARG8
CycL variable ?ARG8
|
static Variable |
Cyc.Constants.ARG9
CycL variable ?ARG9
|
static Variable |
Cyc.Constants.ARGN
CycL variable ?ARGN
|
static Variable |
Cyc.Constants.VAR
CycL variable ?VAR
|
static Variable |
Cyc.Constants.VAR1
CycL variable ?VAR1
|
static Variable |
Cyc.Constants.VAR2
CycL variable ?VAR2
|
static Variable |
Cyc.Constants.VAR3
CycL variable ?VAR3
|
static Variable |
Cyc.Constants.VAR4
CycL variable ?VAR4
|
static Variable |
Cyc.Constants.VAR5
CycL variable ?VAR5
|
static Variable |
Cyc.Constants.VAR6
CycL variable ?VAR6
|
static Variable |
Cyc.Constants.VAR7
CycL variable ?VAR7
|
static Variable |
Cyc.Constants.VAR8
CycL variable ?VAR8
|
static Variable |
Cyc.Constants.VAR9
CycL variable ?VAR9
|
| Modifier and Type | Method and Description |
|---|---|
static Variable |
Variable.get(String varStr)
Creates an instance of #$CycLVariable represented by varStr in the underlying KB.
|
| Modifier and Type | Method and Description |
|---|---|
List<Variable> |
Sentence.getVariables(boolean includeQueryable)
Returns a list of the Variables in the sentence.
|
| Modifier and Type | Method and Description |
|---|---|
Variable |
VariableService.get(String varStr)
Creates an instance of #$CycLVariable represented by varStr in the underlying KB.
|
| Modifier and Type | Class and Description |
|---|---|
class |
VariableWrapper
An abstract base class for implementing Variables per the decorator pattern.
|
| Modifier and Type | Method and Description |
|---|---|
List<Variable> |
SentenceWrapper.getVariables(boolean includeQueryable) |
| Modifier and Type | Method and Description |
|---|---|
Map<Variable,Object> |
QueryAnswer.getBindings()
Get the values to which the all variables are bound.
|
List<Variable> |
QueryResultSet.getColumns()
Returns a list of column Variables that are available.
|
Map<Variable,Paraphrase> |
ParaphrasedQueryAnswer.getParaphrasedBindings() |
Set<Variable> |
QuerySpecification.getQueryVariables()
Returns a Collection of the variables in this query for which bindings are sought.
|
Set<Variable> |
QueryAnswer.getVariables() |
| Modifier and Type | Method and Description |
|---|---|
Query |
ModifiableQuerySpecification.addQueryVariable(Variable var)
Designates var as a variable to return bindings for.
|
void |
ModifiableQuerySpecification.bindVariable(Variable var,
Object replacement)
Bind a query variable to a specified value.
|
int |
QueryResultSet.findColumn(Variable columnVar)
Returns the column index for
variable . |
<O> O |
QueryAnswer.getBinding(Variable var)
Get the value to which the specified variable is bound.
|
Paraphrase |
ParaphrasedQueryAnswer.getBindingParaphrase(Variable var) |
<O> List<O> |
QueryAnswers.getBindingsForVariable(Variable var)
Returns a List of all the values for one variable from all the answers to a query.
|
boolean |
QueryResultSet.getBoolean(Variable columnVar)
Returns, as a
boolean , the value at the current row for variable . |
Date |
QueryResultSet.getDate(Variable columnVar)
Returns, as a
java.sql.Date object, the value in the current row for variable. |
double |
QueryResultSet.getDouble(Variable columnVar)
Returns, as a
double , the value at the current row for variable . |
float |
QueryResultSet.getFloat(Variable columnVar)
Returns, as a
float , the value at the current row for variable . |
int |
QueryResultSet.getInt(Variable columnVar)
Returns, as a
int , the value at the current row for variable . |
<O> O |
QueryResultSet.getKbObject(Variable columnVar,
Class<O> type)
Return the binding for
variable as a KbObject or java primitive, with an
expected type of T . |
long |
QueryResultSet.getLong(Variable columnVar)
Returns, as a
long , the value at the current row for variable . |
<O> O |
QueryResultSet.getObject(Variable columnVar,
Class<O> type)
Return the binding for variable as an instance of type.
|
<O> Optional<O> |
QueryAnswers.getOnlyBindingForVariable(Variable var)
Returns an Optional containing the single value for a single variable from the sole answer (if
present) to a query.
|
String |
QueryResultSet.getString(Variable columnVar)
Returns, as a
String , the value at the current row for variable . |
<O> Set<O> |
QueryAnswers.getUniqueBindingsForVariable(Variable var)
Returns a Set of all unique values for one variable from all the answers to a query.
|
boolean |
QueryAnswer.hasBinding(Variable var)
Does the specified variable have a value in this query answer?
|
Query |
ModifiableQuerySpecification.removeQueryVariable(Variable var)
Designates var as a variable to not return bindings for.
|
List<String> |
QueryAnswers.toBindingsStringsForVariable(Variable var) |
| Modifier and Type | Method and Description |
|---|---|
Query |
ModifiableQuerySpecification.setQueryVariables(Collection<Variable> vars)
Designates vars as the variables to return bindings for.
|
Copyright © 2015–2018 Cycorp, Inc. All rights reserved.


Meet new people close by. Have a nice conversartion. Make friends.
The map shows you people nearby. People around you open for some nice chat, some laughs or even some more.
Make friends and reach them later through Facebook™ for more fun.
We believe you only get to know someone once you talk, that's why you'll get a picture: no name, no age, no more. Stand up and say "hello"!
Use the built-in meeting system to register someone you have met and reach them later.


Tiny Explorer
Search
Address
Balance:
Total Received:
Pending:
# of Transactions:
Transactions
#
Transaction ID
Time


Preparation time
overnight
Cooking time
10 to 30 mins
Serves
Serves 10-14
This cake is made up of homemade coffee biscuits piled into layers with ginger syrup and cream to hold it all together.
Equipment and preparation: you will need a 7cm/2¾in diameter plain biscuit cutter and a 25cm/9in round cake board.
For the ice box coffee biscuits, place the butter and sugar into a bowl and beat until light and fluffy, then add the eggs and beat well.
Add the cold coffee and coffee essence and mix well. Fold in the flour, cocoa, bicarbonate of soda and salt and bring together to form a firm dough.
Press into a 2cm/¾in thick block, then wrap in cling film and place in the fridge for one hour to rest.
Preheat the oven to 180C/350F/Gas 4.
Roll the dough out to 5mm/¼in thick, then stamp out into discs using a 7cm/2¾in diameter plain biscuit cutter.
Place onto a baking tray and bake for 8-10 minutes, or until just risen and firm to touch.
For the cake, whisk the double cream with the coffee essence in a bowl until it just holds soft peaks when the whisk is removed from the bowl, then fold in the stem ginger syrup and coffee essence.

Dollop two spoonfuls of cream in the middle and spread out to within 2cm/¾in of the edge, then place one biscuit in the centre and six around it in a circle. Spread a layer of cream over the top, making sure the biscuits are still visible at the side.
Repeat the process layering up the biscuits like bricks, until you have used up all the cream and all the biscuits, finishing with a layer of cream.
Place in the fridge overnight but preferably for 24 hours so that the biscuits soften.
Decorate the top of the cake with the slices of stem ginger. Serve cut into slices straight from the fridge.


I often receive letters from readers crying plaintively “Mr Key! Mr Key! How can I become a tiptop sporting champion? If anyone can give me a top tip, it is you!”
Actually, it is not me you need to ask, but Hooting Yard's tiptop sports correspondent Fatima Gilliblat. This is what she has to say:
The best way to become a tiptop sporting champion is to ensure you were born on 23 March. It was on this day of the year that champs such as Roger Bannister, Mo Farah, Chris Hoy, Jason Kenny, Steve Redgrave, and the bobsleighing Olympian Shelley Rudman dropped from their mothers' wombs, as did the cricketer Mike Atherton and the pugilist Joe Calzaghe. If you were born on any other day, I am afraid that the road to sporting glory will be steep and pitiless and you will almost certainly fail.


You may use {yourvaluename} in the question and page titles, html question and completedHtml survey property.
The value name can be your question names, pageno (the current page number) and pagecount (visible pages count). The name is case insensitive.
In this example, the default question title template is changed to:
survey.questionTitleTemplate = "{no}) {title} {require}:";
The default requiredText property is changed to:
survey.requiredText = "(*)";
The question No starts from A.
survey.questionStartIndex = "A";


| 1 | /* | |
| 2 | * Copyright 2010 The Closure Compiler Authors. | |
| 3 | * | |
| 4 | * Licensed under the Apache License, Version 2.0 (the "License"); | |
| 5 | * you may not use this file except in compliance with the License. | |
| 6 | * You may obtain a copy of the License at | |
| 7 | * | |
| 8 | * http://www.apache.org/licenses/LICENSE-2.0 | |
| 9 | * | |
| 10 | * Unless required by applicable law or agreed to in writing, software | |
| 11 | * distributed under the License is distributed on an "AS IS" BASIS, | |
| 12 | * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | |
| 13 | * See the License for the specific language governing permissions and | |
| 14 | * limitations under the License. | |
| 15 | */ | |
| 16 | ||
| 17 | package com.google.javascript.jscomp; | |
| 18 | ||
| 19 | import com.google.javascript.rhino.Node; | |
| 20 | ||
| 21 | /** | |
| 22 | * A compiler pass that just reports an error. | |
| 23 | * | |
| 24 | */ | |
| 25 | ||
| 26 | class ErrorPass implements CompilerPass { | |
| 27 | private final AbstractCompiler compiler; | |
| 28 | private final JSError error; | |
| 29 | ||
| 30 | ErrorPass(AbstractCompiler compiler, DiagnosticType error) { | |
| 31 | this(compiler, JSError.make(error)); | |
| 32 | } | |
| 33 | ||
| 34 | ErrorPass(AbstractCompiler compiler, JSError error) { | |
| 35 | this.compiler = compiler; | |
| 36 | this.error = error; | |
| 37 | } | |
| 38 | ||
| 39 | @Override | |
| 40 | public void process(Node externs, Node root) { | |
| 41 |
1
1. process : removed call to com/google/javascript/jscomp/AbstractCompiler::report → KILLED |
compiler.report(error); |
| 42 | } | |
| 43 | } | |
Mutations | ||
| 41 |
1.1 |


Is your community lacking a Self Help Group(SHG) community ? Want to have a government backed SHG group you can use to support your local community ? Do you want to have a self supported society?
You can create your own community
Are you searching for an existing Self Help Group(SHG) in your society? Do you want to be a part of a government trusted community for economic security?
You can join an existing community
Is your community lacking a Self Help Group(SHG) community ? Want to have a government backed SHG group you can use to support your local community ? Do you want to have a self supported society?
Log in to your existing community


Home      Survivors     Family and Friends      Other Information    About us
What to Know about Sexual Assault
Our Pledge
Who are you?
I am...
an assault survivor:
a family member or friend:           looking for information:
There are many ways to help yourself heal. Find out some of the ways you can do this.
Learn about different ways to help your loved ones, and decide what technique is best for them.
Click here for information about current advocacy efforts, statistics, and places to go for more information.
The Concept Crew, 2016
Rebecca Levy, Emma James, Jasmine Okebugwu, Fawziyah Alebi


Tensorflow in Swift
Using Swift on Tensorflow
- Lauching a Jupyter notebook for Swift
git clone https://github.com/google/swift-jupyter.git cd swift-jupyter docker build -f docker/Dockerfile -t swift-jupyter . docker run -p 8888:8888 -it --cap-add SYS_PTRACE -v ~/swift-notebooks:/notebooks swift-jupyter
- Useful resources:
- Swift for Tensorflow project on github: https://github.com/tensorflow/swift
- Swift kernels in Jupyter: https://github.com/google/swift-jupyter/#option-3-using-the-docker-container
- Fast AI swift notebooks: https://github.com/fastai/fastai_docs/tree/master/dev_swift
- Hacking with Swift: https://www.hackingwithswift.com
- Swift for Tensorflow example: https://colab.research.google.com/github/tensorflow/swift/blob/master/docs/site/tutorials/model_training_walkthrough.ipynb


Junichi Masuda
Game composer, director of game development, game designer, game producer and programmer, known for his work on the Pokémon franchise. He is a member of the board of directors of Game Freak, where he has been working since 1989. Prior to starting work on the Pokémon series of games, he helped write music for the Mendel Palace and Smart Ball games. In developing the first game in this series, Pokémon Red and Green, he took part as a composer and creator of sound effects, and also took on part of the programming work.


Main page
Demo
Documentation
Contact
Super
form
If you want to have a great looking form try new one jQuery lib to style default controls.
Checkboxe
What type of music do you like most?
Rock
Pop
Jazz
Hip hop
Rap
Classic
Soul
Latino
Radio
What is Your favourite sport?
Badminton
Ultimate Frisbee
Football
Volleyball
Basketball
Hokey
Tenis
Swimming
Select
What character from Star Wars do you like most?
- wybierz -
Anakin
Luke
Obi Wan Kenobi
Leia
Padme Amidala
Yoda
Darth Veder
R2D2
What do you feel now?
Anger
Happy
Sad
Relax
Tired
Love
Hate
Confused
Satisfy


You are currently in {{selectedInventory.Name}}. To change, you can always click here.
Active Inventory :
{{selectedInventory.Name}}
{{route.DisplayName}}


June 2, 1999 update from Dennis McKennaTo all,
This is a followup update on Terence's situation, and will include many of you who have emailed in following the sending of the first and second updates. I tried to include everyone who asked to be included, if I've left you off, its due to oversight and not any attempt to exclude *anyone* from being involved in the process of healing, love, and support that has literally poured in since news of this sad development. I'm doing my best to stay on top of these lists but the process has been sporadic and imperfect due to being focused on what is happening right here and now with Terence. More about logistics later.
First, I want everyone to know that Terence knows of your love and support, all the messages coming in from many quarters and so many people, and he is moved by this outpouring. He sends all of you his love in return, and in characteristic fashion, tells everyone not to worry. Right now Terence is spending his time with his closest friends and family. Finn, his son, is here with him, as is his brother, yours truly Dennis, as well as his new lover and some of his oldest and closest friends. We are spending quality time and just trying to love him as much as possible while at the same time we try to sort through very complex sets of options, decisions, etc. regarding his immediate treatment and followup treatment. Terence is in good spirits, even though he has the disease his meds are keeping him stabilized and he looks normal and "fit as a fiddle" as he would say. His humor, irreverance, and bemused perspective continues to sustain not only him but those around him, and continues unabated.
If you want to send any non-electronic messages to Terence (no packages please) you can send them to:
Terence McKenna
c/o Levity
P.O. Box 1013
Cooper Station, New York, NY 10276-1013
We are working on getting a website set up where people will be able to read further updates on Terence's condition and progress. We will send out that information when we have it, probably in the next update, and then after that these email postings will become less frequent as most will be able to access the information from the website. Communications from family members, close friends, can still be directed to this address and I will do my best to respond. Communications from T's many friends and admirers are also welcome but I may not be able to respond; rest assured I am getting many messages and these will be passed along to T as best possible. I know everyone is concerned for Terence and the expressions are appreciated, but please do me the favor of not overwhelming my email box; the time I spend dealing with email is time I'm not spending with Terence and that is what I need to be doing right now. Besides these updates, and the webpage at levity.com which will be up shortly, Terences' condition is being discussed in several mailing lists, including the Novelty List, the Entheogen List, etc.
Also want to express our thanks and appreciation to the many people who have contacted us with information on experimental therapies, different treatment modalities, (both alternative and "conventional"), names of neurosurgeons, website URLS, database searches, etc. There is a tremendous amount of information and much of it is difficult to evaluate under the best of circumstances. We do appreciate you sending that kind of information, but ask you to rest assured that we are ignoring none of it, we are looking into all of it in consultatation with our doctors, who are both very compassionate and very knowledgable, and with such outside help, second opinions, additional info, etc. as we need. Its all available to us and we are looking at many of them very seriously. Because Terence's condition (glioblastoma) is such an intractable condition for which there are no really "good" therapies, (alternative or conventional) there are literally thousands of different treatments; that's becuase none of them seem to work very well.
So, I know that your suggestions for treatment, further contacts, leads to literature, etc. are all well meant and come from the heart, and we appreciate them. At the same time, I ask you to "trust in the process" and to respect our judgements when it comes down to what decisions must be made for Terence's treatment, both in the immediate days ahead and over a longer term of several months. Its always easy to second-guess a physician's judgement on a particular patient when you are separated from the process and do not have all the information that is available to the physician, to Terence, and to his family, and may have certain preferences or beliefs regarding various treatment modalities. I ask you, we ask you, to please not do that. Rest assured, we have an excellent relationship with our physician, Dr. Keep, we are working with him closely on all of the immediate and followup treatment options, we are consulting with other medical and alternative practitioners as needed, and Dr. Keep is in the loop and a valued consultant on *everything* and we feel that he has a similar respect and compassion for us.
Having said all that I can outline the consensus we have reached as to what is to be done for Terence over the next week. After evaluating many possible alternatives, both in terms of treatment approaches and where the treatment should be carried out, we have agreed to what Dr. Keep, with the concurrence of his case review board, has recommended as the least invasive, least disruptive treatment that will be effective in the short term, afford maximum length and quality of life, and will not compromise Terence's options or eligibility for further followup treatments, experimental treatments, etc.
Dr. Keep's review board agrees with him, and so do we, that at this point the use of what is called the "gamma knife" essentially a focused gamma ray treatment, to kill the main tumor mass, followed by "soft" radiation therapy (focused x-ray treatments) to kill the "mycelium" the remaining tendrils of cancer cells which are diffusely embedded in the brain, over a period of about 1 month, is the best of a number of treatment options. It is less risky than surgery in terms of the potential for immediate damage to collatoral areas, leading to neurological impairment and/or death on the operating table due to hemmorrhage. The procedure is non-invasive, can be done on an outpatient basis, and, with the followup radiotherapy, has just as good a chance as surgery at maximum prolongation of life and preservation of quality of life, with significantly fewer immediate risks. There is a small but real possibility that the gamma knife treatment will result in further swelling of the tumor which may necessitate additional followup surgery. But the doctor feels that the risks are small and within reasonable limits. So at this time, Terence is scheduled to have this procedure performed on Tuesday afternoon; they will keep him in H0nolulu for the next week (though not in the hospital) to monitor the situation. Over this time we will also be sorting out the logistics of the next step in the therapy, the month to six weeks of followup radiotherapy. That must be initiated quickly, as well, and we are evaluating options as to where and when this will be done. While all this is going on we will continue to gather information and evaluate it with respect to chemotherapeutic treatments, alternative treatments, clinical and experimental studies, and also what options may exist for treating the tumor when it recurs, which unfortunately is nearly an inevitability for this type of tumor.
We will keep you posted of course and through a variety of means, including these periodic if somewhat irregular updates, at levity.com and various mailing lists.
Keep sending those gift waves and hold thoughts of Terence and love in your hearts. If you think of it give him a special extra prayer and blessing on Tuesday when he has the procedure.
This is his brother and soulmate, Dennis
Love to all.


My personal website highlights my curiosity in the field of computer science: artificial intelligence, machine learning, research, and software engineering.
TThis past summer, I worked as a software engineering intern at Dell Technology. Worked in a team of 3 to build and test a universal crawler connector using Java and Python to store crawler’s data in ServiceNow platform. Our internship project reduced development time for new crawlers by 60% and reduced existing crawler’s codebase by 35%. Designed the software architecture of the tool by creating Data flow, UML, and Sequence diagrams.
As a result of yearlong research with Prof. Edward Rietman of UMass Amherst, my honors thesis was approved and published by the Commonwealth Honors College. The research was on developing a convolutional neural network and decision tree algorithm using Python to analyze and compute fractal dimensions of MRI images to diagnose and determine the stage of brain and breast tumor with an accuracy of > 80%.
Graduating December 2021 from the University of Massachusetts Amherst with a master’s in computer science with data science concentration. Currently looking for full time data science and software engineering opportunities from January 2022.
Skills: Java, Python, data science, Machine Learning, Artificial Intelligence, Neural Networks, Project Management, Strategy, Backend development
• Built and tested universal crawler connector using Java and Python which reduced development time for new crawlers by 60% and existing crawler’s codebase by 35%
• Designed the software architecture of the tool by creating Data flow, UML, and Sequence diagrams
• Deployed crawler to collect and parse system data of 10,000+ servers to store in ServiceNow platform which achieved a simplistic and aggregated view for customers and employees’ consumption
• Engineered and tested the crawler using Java, Spring boot framework, Jenkins, Swagger, JUnit, and integration testing
• Assisted professor to teach AI course for 4 semesters with 160+ students by leading lab assignments, facilitating group discussions, and answering course-related coding and theoretical questions
• Supervised 3-member cross-functional team using agile methodology to create a social networking and recruiting platform based on people’s unique skill/talent which led to an initial seed funding
• Prototyped desktop and smartphone application using Java, Swift, and Python
• Implemented a feature for an existing asset management tool using Java that uses algorithm to automatically calculate 2,800+ employees’ efficiency and ROI to generate KPI dashboards using Google big query and SQL commands for team managers
• Developed software using C++ to pilot a forward collision warning system with the integration of LIDAR sensor and Arduino
• Presented deliverables to C-level board, which resulted in the prototype being implemented by the development team in Taiwan
Related courses: : Reinforcement Learning (F21), Neural Networks, Algorithms for Data Science, Artificial Intelligence, Machine Learning, Intro to NLP
Related courses: Search Engines, Intro to Algorithms, Software Engineering, Intro to Computer Vision, Computer Systems Principles, Programming w/Data Structures, Intro Linear Algebra, Multivariate Calculus
Engineered 5-layer feed-forward neural network with a combination of supervised and unsupervised learning techniques using Python for automatic speaker identification with an accuracy of 94%
View PaperDeveloped convolutional neural network and decision tree algorithm using Python to analyze and compute fractal dimensions of MRI images to diagnose and determine the stage of brain and breast tumor with an accuracy of > 80%. Published honors thesis after successfully defending the thesis to the Commonwealth Honors College
View ThesisCreated an application that detects and alerts drowsy drivers by extracting and analyzing eye coordinates using OpenCV library and also by using a ML model trained with a dataset of 15,000+ people’s face.
View ProjectImplemented iOS and Android app to guide visually impaired people along the Milford’s trail using Bluetooth low energy (BLE) beacon technology and smartphone camera, coded using swift, java, and with the use of OpenCV library
Built a web application using JavaScript and HTML to automatically identify known faces with 90% accuracy using facial detection and recognition to help people affected by Alzheimer's disease.
View ProjectCreated a working prototype of an iOS application using swift and objective-C that provides cheap, safe, and convenient travel plans for students. Won amongst 75+ participating teams for best iOS app that was designed and coded in less than 48 hours.
View ProjectCreated software to convert 15+ American sign language hand gestures to computer generated voice using java, python and Leap Motion’s IR technology.
View ProjectDesigned and launched, “Town of Holliston’s Smartphone App” (iOS and Android), which is endorsed by the Board of Selectmen as the town’s official app impacting 13,500+ residents. Developed using swift, objective-C, java, and integrated with Parse database for dynamic content and offline support.
View Project


cease & desist letter #12 - Futurama
An archive of disturbing illustration
Part I. Cause
Futurama Porn!
Part II. Conclusion
OK, perhaps that was over the top..
[
return to rotten.com
]


Eighth Conference of the Parties to the UN Framework Convention on Climate Change
30-Oct-02 — original report
Chair Thorgeirsson opened the sixth session of SBSTA-17, held in the afternoon.
On election of officers, delegates elected Arthur Rolle (Bahamas) as SBSTA Vice-Chair and Tatyana Ososkova (Uzbekistan) as SBSTA Rapporteur.
On the relationship between efforts to protect the stratospheric ozone layer and to safeguard the global climate system, Richard Bradley (US) reported on informal consultations.
SBSTA adopted the draft conclusions and agreed to forward a draft decision to the COP (FCCC/SBSTA/2002/L.19 and Add.1).
Jimena Nieto (Columbia) reported on consultations.
SBSTA adopted draft conclusions noting the terms of reference for a workshop, and agreed to transmit a draft decision to the COP (FCCC/SBSTA2002/L.18 and Add.1).
Fatou Gaye (Gambia) and Jean-Pascal van Ypersele (Belgium) reported on the work of the contact group.
Parties adopted conclusions (FCCC/SBSTA/2002/L.23).
On the draft COP-8 decision, delegates diverged on the text relating to the financial mechanism.
Following protracted discussions, delegates agreed to forward the draft decision to the COP (FCCC/SBSTA/2002/L.23/Add.1).
Terry Carrington (UK) and Philip Gwage (Uganda) reported on consultations on development and transfer of technologies.
Delegates adopted conclusions and approved a COP-8 decision (FCCC/SBSTA/2002/L.29 and Add.1), following amendment to both texts.
Suk-Hoon Woo (Republic of Korea) reported on consultations, noting that the group was unable to reach consensus.
SBSTA Chair Thorgeirsson said that informal consultations on this issue were also unsuccessful, noting that the G-77/China was concerned about how Article 2.3 would be reflected in the conclusions.
He introduced draft conclusions that took note of the oral report and other documents under consideration.
SAUDI ARABIA said that there was no agreement on these conclusions and proposed replacing all paragraphs with text noting that SBSTA had not completed its consideration of issues under this item, but agreed to continue consideration at SBSTA-18.
The EU proposed making reference to the implementation of decision 13/CP.7 (P&Ms).
The conclusions were adopted as amended (FCCC/SBSTA/2002/L.28).
Sue Barell (Australia) reported on the consultations.
She outlined draft conclusions, noting the need for strong collaboration and coordinated approaches between research and other bodies.
The conclusions were adopted without amendment (FCCC/SBSTA/2002/L.27).
Cleaner or less greenhouse gas-emitting energy: Chair Thorgeirsson said that consultations on this issue did not result in substantive conclusions.
SBSTA adopted conclusions deferring further consideration of the issue to SBSTA-18 (FCCC/SBSTA/2002/L.25).
On adverse effects of P&Ms, Chair Thorgeirsson reported that consultations had not resulted in substantive conclusions.
SBSTA adopted conclusions deferring further consideration of the issue to SBSTA-18 (FCCC/SBSTA/2002/L.26).
The report on the session was adopted (FCCC/SBSTA/2002/L.13).
Chair Thorgeirsson then closed SBSTA-17.
Chair Estrada opened the session at 11:45 pm.
The Secretariat introduced the available draft conclusions.
The SBI adopted conclusions on arrangements for intergovernmental meetings for: COP/MOP-1 (FCCC/SBI/2002/L.16 and Add.1); the date and venue of COP-9 (FCCC/SBI/2002/L.10); and effective participation in the UNFCCC process (FCCC/SBI/2002/L.13), recording that the EU did not agree with the last conclusions as the text had not previously been discussed. Parties agreed on conclusions on Annex I national communications (FCCC/SBI/2002/L.9) and on administrative and financial matters (FCCC/SBI/2002/L.7).
They decided to continue discussing the request by the CACAM at the next SBI session, noting that the CACAM can access GEF funding.
It was also decided to continue consideration of the Croatian proposal on LULUCF and its special circumstances (FCCC/SBI/2002/L.11 and L.12).
On capacity-building, Parties made amendments to and adopted conclusions (FCCC/SBI/2002/L.15), soliciting Party submissions with a view to reaffirming the current framework contained in two COP-7 decisions. On implementation of Article 4.8 and 4.9, SBI adopted conclusions on progress in the implementation of activities under decision 5/CP.7 on adverse effects (FCCC/SBI/2002/L.17), and on matters related to LDCs (FCCC/SBI/2002/L.8).
It was agreed that the SB Chairs and Secretariat would make arrangements for a meeting on implementation of Article 4.8 and 4.9, to be held back-to-back with a workshop on cooperation with international organizations agreed by the SBSTA.
Chair Estrada adjourned the session due to the late hour.
The SBI will meet again at a time yet to be decided.
Parties adopted conclusions with minor amendments on consideration of how the TAR could facilitate the work of the SBSTA (FCCC/SBSTA/2002/L.20).
SBI Chair Estrada convened the contact group in the morning.
On the report of the GEF, INDIA, opposed by the EU, CANADA and SWITZERLAND, requested the deletion of text emphasizing the 'successful and substantial third GEF replenishment.
' On behalf of the G-77/CHINA, he proposed text stressing the effective operationalization of the recently established funds and the greater effectiveness of existing funds.
Parties could not agree on the proposals. On guidance to the Special Climate Change Fund, CANADA, SWITZERLAND, NEW ZEALAND, AUSTRALIA, and JAPAN supported using a new text proposed by the EU as the basis for negotiations.
INDIA, for the G-77/CHINA, preferred using the Chair's text.
CANADA, with SWITZERLAND, stressed the prioritization of guidance to the Fund.
NORWAY and the EU underscored their support for operationalizing the Fund, stressing the importance of identifying priorities and following similar procedures used in establishing the Least Developed Country (LDC) Fund.
Parties could not agree on providing guidance on the Special Climate Change Fund to the financial mechanism for now, and agreed on an EU proposal to consider Party submissions and discussions at SB-18 and a decision at COP-9. On the LDC Fund, delegates discussed the Canadian proposal, noting that it contained specific elements for the organization of four regional workshops and the initiation of a dialogue on next steps in the national adaptation programmes of action (NAPA) implementation process.
MALI requested Annex I Parties to consider capacity-building for focal points and the implementation of NAPAs.
SAMOA stressed language on the complementarity of the Funds and the operational guidance from the COP.
Following informal consultations, the draft decision on guidance to the LDC Fund was agreed with minor additions.
On the provision of additional guidance to the GEF, several Parties requested this discussion be delayed until guidance from the contact groups on capacity- building, technology transfer, UNFCCC Articles 4.8 & 4.9 (adverse effects), and Article 6 could be received. Regarding the review of the financial mechanism, the EU expressed concern with moving forward on the basis of the Chair's draft decision and distributed a new proposal.
Parties could not agree to an EU proposal requesting the Executive Secretary and the GEF to explore synergies between the review processes of the UNFCCC and the GEF, and deleted this paragraph.
On additional guidance to the operational entity of the financial mechanism, Chair Estrada invited comments on matters related to capacity-building and technology transfer.
Parties could not agree to the elements in the draft text.
Following informal consultations, Parties met in the afternoon to discuss the improved guidelines for non-Annex I national communications.
Group Chair José Romero (Switzerland) reminded delegates that unless agreement is reached on the improved guidelines, the second national communications will be prepared using current guidelines.
Working through the text, delegates debated the starting year of non-Annex I Parties' greenhouse gas inventories, the frequency of the submissions, how to address years where data is incomplete or missing, and submissions by LDCs.
Parties left text bracketed and turned to emissions factors, disagreeing over reference to 'develop and use' or just 'use' country-specific or regional emissions factors, with some Parties preferring to retain reference to 'develop' in the operational text, and others favoring placing this in the decision text.
Discussions continued late into the night.
The corridors remained empty as delegates attempted to complete their overloaded tasks late into the night prior to the arrival of Ministers for a stock-taking session Wednesday afternoon.
The subdued mood in the corridors and the slow movement in the SB sessions left several observers questioning the final form the Delhi Declaration and its impact on the outstanding contentious issues.
Review of methodological work: Harald Dovland (Norway) reported on the informal consultations on this issue and presented draft conclusions (FCCC/SBSTA/2002/L.17).
CHINA said he had been unable to take part in the consultations, and proposed several substantive amendments.
BANGLADESH, for the G-77/CHINA, noted that the G-77/China had discussed the issues internally and accepted these conclusions.
A revised text was agreed at the end of the SBSTA meeting, following informal consultations.
On guidelines under Protocol Articles 5 (methodological issues), 7 (communication of information) and 8 (review of information), Helen Plume (New Zealand) reported that the contact group had completed its work, bringing three years of negotiations on this issue to a close.
Murray Ward (New Zealand) reported on informal consultations on guidelines under Article 7.4 (registries).
The conclusions were adopted and draft decisions forwarded to the COP (FCCC/SBSTA/2002/L.15 and Add.
BOLIVIA noted its reservation with regard to identifying certified emission reductions (CERs) acquired as a result of afforestation and reforestation under the CDM separately from other CERs.
Parties adopted conclusions without amendment (FCCC/SBSTA/2002/L.16).
Parties adopted conclusions and a draft COP-8 decision without amendment (FCCC/SBSTA/2002/L.21 and Add.1).
Thelma Krug (Brazil) reported on the contact group.
She drew attention to conclusions, noting, inter alia, an options paper on sinks under CDM prepared by the Secretariat and a workshop to be held in February 2003.
She said that Brazil offered to host the workshop.
Parties adopted the draft conclusions (FCCC/SBSTA/2002/L.22).
Murray Ward reported on the outcomes of consultations on this issue.
SBSTA adopted conclusions (FCCC/SBSTA/2002/L.24).
On the special circumstances of Croatia under UNFCCC Article 4.6 (special circumstances of economies in transition), Jim Penman (UK) reported on informal consultations.
SBSTA adopted draft conclusions which note that the procedure used by Croatia to estimate its base year emissions is neither consistent with IPCC Good Practice Guidance, nor with UNFCCC reporting guidelines (FCCC/SBSTA/2002/L.14).


Default Title
View all pets
Logout
Name
Age
Size
Spayed/Neutered
Ideal Family
Personality
Vocal
Species
Breed
Adoption Status
Potty trained
Color
Gender
Training/Tricks
Good with children
Good with cats
Dog friendly
Rescue name
Contact Rescue
Location
Interests
About


|
GrPPI
0.3.1
Generic and Reusable Parallel Pattern Interface
|
#include <dynamic_execution.h>
Public Member Functions | |
| dynamic_execution () noexcept | |
| template<typename E > | |
| dynamic_execution (const E &e) | |
| bool | has_execution () const |
| template<typename... InputIterators, typename OutputIterator , typename Transformer > | |
| void | map (std::tuple< InputIterators... > firsts, OutputIterator first_out, std::size_t sequence_size, Transformer &&transform_op) const |
| Applies a trasnformation to multiple sequences leaving the result in another sequence. More... | |
| template<typename InputIterator , typename Identity , typename Combiner > | |
| auto | reduce (InputIterator first, std::size_t sequence_size, Identity &&identity, Combiner &&combine_op) const |
| Applies a reduction to a sequence of data items. More... | |
| template<typename... InputIterators, typename Identity , typename Transformer , typename Combiner > | |
| auto | map_reduce (std::tuple< InputIterators... > firsts, std::size_t sequence_size, Identity &&identity, Transformer &&transform_op, Combiner &&combine_op) const |
| Applies a map/reduce operation to a sequence of data items. More... | |
| template<typename... InputIterators, typename OutputIterator , typename StencilTransformer , typename Neighbourhood > | |
| void | stencil (std::tuple< InputIterators... > firsts, OutputIterator first_out, std::size_t sequence_size, StencilTransformer &&transform_op, Neighbourhood &&neighbour_op) const |
| Applies a stencil to multiple sequences leaving the result in another sequence. More... | |
| template<typename Input , typename Divider , typename Solver , typename Combiner > | |
| auto | divide_conquer (Input &&input, Divider &÷_op, Solver &&solve_op, Combiner &&combine_op) const |
| Invoke Divide/conquer pattern. More... | |
| template<typename Input , typename Divider , typename Predicate , typename Solver , typename Combiner > | |
| auto | divide_conquer (Input &&input, Divider &÷_op, Predicate &&predicate_op, Solver &&solve_op, Combiner &&combine_op) const |
| Invoke Divide/conquer pattern. More... | |
| template<typename Generator , typename... Transformers> | |
| void | pipeline (Generator &&generate_op, Transformers &&...transform_ops) const |
| Invoke Pipeline pattern. More... | |
|
inlinenoexcept |
|
inline |
| auto grppi::dynamic_execution::divide_conquer | ( | Input && | input, |
| Divider && | divide_op, | ||
| Solver && | solve_op, | ||
| Combiner && | combine_op | ||
| ) | const |
Invoke Divide/conquer pattern.
| Input | Type used for the input problem. |
| Divider | Callable type for the divider operation. |
| Solver | Callable type for the solver operation. |
| Combiner | Callable type for the combiner operation. |
| ex | Sequential execution policy object. |
| input | Input problem to be solved. |
| divider_op | Divider operation. |
| solver_op | Solver operation. |
| combine_op | Combiner operation. |
| auto grppi::dynamic_execution::divide_conquer | ( | Input && | input, |
| Divider && | divide_op, | ||
| Predicate && | predicate_op, | ||
| Solver && | solve_op, | ||
| Combiner && | combine_op | ||
| ) | const |
Invoke Divide/conquer pattern.
| Input | Type used for the input problem. |
| Divider | Callable type for the divider operation. |
| Predicate | Callable type for the stop condition predicate. |
| Solver | Callable type for the solver operation. |
| Combiner | Callable type for the combiner operation. |
| ex | Sequential execution policy object. |
| input | Input problem to be solved. |
| divider_op | Divider operation. |
| predicate_op | Predicate operation. |
| solver_op | Solver operation. |
| combine_op | Combiner operation. |
|
inline |
| void grppi::dynamic_execution::map | ( | std::tuple< InputIterators... > | firsts, |
| OutputIterator | first_out, | ||
| std::size_t | sequence_size, | ||
| Transformer && | transform_op | ||
| ) | const |
Applies a trasnformation to multiple sequences leaving the result in another sequence.
| InputIterators | Iterator types for input sequences. |
| OutputIterator | Iterator type for the output sequence. |
| Transformer | Callable object type for the transformation. |
| firsts | Tuple of iterators to input sequences. |
| first_out | Iterator to the output sequence. |
| sequence_size | Size of the input sequences. |
| transform_op | Transformation callable object. |
[get<I>(firsts), next(get<I>(firsts),sequence_size))
are valid. [first_out, next(first_out,sequence_size)]
are valid. | auto grppi::dynamic_execution::map_reduce | ( | std::tuple< InputIterators... > | firsts, |
| std::size_t | sequence_size, | ||
| Identity && | identity, | ||
| Transformer && | transform_op, | ||
| Combiner && | combine_op | ||
| ) | const |
Applies a map/reduce operation to a sequence of data items.
| InputIterator | Iterator type for the input sequence. |
| Identity | Type for the identity value. |
| Transformer | Callable object type for the transformation. |
| Combiner | Callable object type for the combination. |
| first | Iterator to the first element of the sequence. |
| sequence_size | Size of the input sequence. |
| identity | Identity value for the reduction. |
| transform_op | Transformation callable object. |
| combine_op | Combination callable object. |
[first,last)
are valid. | void grppi::dynamic_execution::pipeline | ( | Generator && | generate_op, |
| Transformers &&... | transform_ops | ||
| ) | const |
Invoke Pipeline pattern.
| Generator | Callable type for the generator operation. |
| Transformers | Callable types for the transformers in the pipeline. |
| generate_op | Generator operation. |
| transform_ops | Transformer operations. |
| auto grppi::dynamic_execution::reduce | ( | InputIterator | first, |
| std::size_t | sequence_size, | ||
| Identity && | identity, | ||
| Combiner && | combine_op | ||
| ) | const |
Applies a reduction to a sequence of data items.
| InputIterator | Iterator type for the input sequence. |
| Identity | Type for the identity value. |
| Combiner | Callable object type for the combination. |
| first | Iterator to the first element of the sequence. |
| sequence_size | Size of the input sequence. |
| last | Iterator to one past the end of the sequence. |
| identity | Identity value for the reduction. |
| combine_op | Combination callable object. |
[first,last)
are valid. | void grppi::dynamic_execution::stencil | ( | std::tuple< InputIterators... > | firsts, |
| OutputIterator | first_out, | ||
| std::size_t | sequence_size, | ||
| StencilTransformer && | transform_op, | ||
| Neighbourhood && | neighbour_op | ||
| ) | const |
Applies a stencil to multiple sequences leaving the result in another sequence.
| InputIterators | Iterator types for input sequences. |
| OutputIterator | Iterator type for the output sequence. |
| StencilTransformer | Callable object type for the stencil transformation. |
| Neighbourhood | Callable object for generating neighbourhoods. |
| firsts | Tuple of iterators to input sequences. |
| first_out | Iterator to the output sequence. |
| sequence_size | Size of the input sequences. |
| transform_op | Stencil transformation callable object. |
| neighbour_op | Neighbourhood callable object. |
[get<I>(firsts), next(get<I>(firsts),sequence_size))
are valid. [first_out, next(first_out,sequence_size)]
are valid.