1.1.1

Note: Use the EXPLAIN command and view the generated query plan to verify that case insensitive
index searches are used where needed.
For columns that are not part of an index, SQLFire observes case-sensitivity only if it is explicitly required (for
example, if the query specifies UPPER(column-name='UPPERCASE_VALUE').
Queries that use the OR clause to perform comparisons on columns of a case-sensitive index must use the UPPER
function on those columns to ensure correct results.
Example
Create an index on two columns:
CREATE INDEX idx ON FLIGHTS (flight_id ASC, segment_number
DESC);
Create a case-insensitive index:
CREATE INDEX idx ON FLIGHTS (flight_id ASC, segment_number
DESC) -- SQLFIRE-PROPERTIES caseSensitive=false <return>
;
CREATE PROCEDURE
Creates a Java stored procedure that can be invoked using the CALL statement.
Syntax
CREATE PROCEDURE
procedure-name
([ procedure-parameter [, procedure-parameter] * ])
LANGUAGE JAVA
PARAMETER STYLE JAVA
{ NO SQL | CONTAINS SQL | READS SQL DATA | MODIFIES SQL DATA }
[ [DYNAMIC]
RESULT SETS
integer]
EXTERNAL NAME 'procedure_external_class.method'
Description
CREATE PROCEDURE creates a Java stored procedure that can be invoked using the CALL on page 474
statement. A procedure is invoked on the current member. Because the procedure is written in Java code, it can
invoke SQL commands using JDBC internally. A qualified procedure name cannot use the SYS schema, which
is reserved for internal usage. The following sections describe the syntax.
procedure-name
[schemaName.]SQL92Identifier
If schemaName is not provided, the current schema is used as the the default schema. If a qualified procedure
name is specified, the schema name cannot begin with SYS.
procedure-parameter
[ { IN | OUT | INOUT } ] [ parameter-name ] data-type
The default value for a parameter is IN. parameter-name must be unique within a procedure.
vFabric SQLFire User's Guide488
vFabric SQLFire Reference