![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Product Manuals » ElevateDB Version 2 Manual for Delphi 7 » DBISAM Migration » Statements |
Removed | Description |
EMPTY TABLE | This statement is no longer supported. ElevateDB requires that you use the DELETE statement to remove all rows from a table. |
VERIFY TABLE | This statement is no longer supported. ElevateDB currently only offers repair facilities by using the REPAIR TABLE statement. |
UPGRADE TABLE | This statement is no longer necessary. |
START TRANSACTION COMMIT ROLLBACK | These statements are now considered part of the ElevateDB SQL/PSM support and are only allowed in jobs, procedures, functions, and triggers. Outside of SQL/PSM, use the TEDBDatabase StartTransaction, Commit, and Rollback |
Changed | Description |
SELECT | ElevateDB supports single-row query expressions as values in the list of selected columns. The INTO clause is no longer supported. ElevateDB uses the standard SQL CREATE TABLE AS clause to create a table using a query expression. The EXCLUSIVE clause is no longer necessary. With ElevateDB you can use the actual table name or the table correlation name in column references anywhere in the SELECT statement. ElevateDB supports single-row query expressions as values in the JOIN clauses. ElevateDB does not optimize join expressions in the WHERE clause, otherwise known as SQL-89 style joins. You must use the JOIN clause in order to have ElevateDB optimize the joins. ElevateDB supports correlated sub-queries in the WHERE clause. ElevateDB supports single-row query expressions as values in the WHERE clause. The GROUP BY, HAVING, and ORDER BY clauses in ElevateDB support any type of expression, and may refer to columns that aren't in the SELECT list. The GROUP BY and ORDER BY clauses no longer support ordinal values as a way to specify a SELECT column position in the list of SELECT column expressions. You must specify the actual column reference or expression. The NOCASE clause is no longer necessary in the ORDER BY clause. ElevateDB uses the COLLATE clause to specify the collation for an ORDER BY expression. Please see the Internationalization topic for more information. The TOP clause is no longer supported. ElevateDB will introduce standard WINDOW clause support for selecting ranges of rows in a later release. The LOCALE clause is no longer necessary. ElevateDB supports column-level collations. Please see the Internationalization topic for more information. The ENCRYPTED WITH clause is no longer supported. |
INSERT | The EXCLUSIVE clause is no longer necessary. The COMMIT clause is no longer supported. ElevateDB internally determines the optimal commit interval for lengthy INSERT statements. |
UPDATE | The EXCLUSIVE clause is no longer necessary. The FROM clause is no longer supported. ElevateDB can use correlated sub-queries in the UPDATE values and/or WHERE clause. The COMMIT clause is no longer supported. ElevateDB internally determines the optimal commit interval for lengthy UPDATE statements. The NOJOINOPTIMIZE clause is no longer supported. The JOINOPTIMIZECOSTS clause is no longer supported. |
DELETE | The EXCLUSIVE clause is no longer necessary. The FROM clause is no longer supported. ElevateDB can use correlated sub-queries in the WHERE clause. The COMMIT clause is no longer supported. ElevateDB internally determines the optimal commit interval for lengthy DELETE statements. The NOJOINOPTIMIZE clause is no longer supported. The JOINOPTIMIZECOSTS clause is no longer supported. |
CREATE TABLE | The IF NOT EXISTS clause is no longer supported. ElevateDB uses catalog queries to determine if a table exists. Please see the System Information topic for more information. The column definition NULLABLE clause is no longer supported. To make a column nullable in ElevateDB, don't include the NOT NULL clause. The column definition DEFAULT clause accepts any basic expression in ElevateDB. A column definition may now include a GENERATED clause to specify that the column is a generated column. Generated columns can be generated as sequence numbers or expressions. The column definition MIN and MAX clauses are no longer necessary. ElevateDB supports column constraints via the CHECK clause. ElevateDB allows for specifying primary key, unique key, and foreign key constraints in a column definition. The CHARCASE clause is no longer supported. The COMPRESS clause has been renamed to COMPRESSION and moved so that it is next to the data type definition. The NOCASE clause is no longer necessary in a primary key, unique key, or foreign key (new) constraint definition. ElevateDB uses the collation defined for the column in the column definition for determining the collation of these types of constraints. Please see the Internationalization topic for more information. The DESC and ASC clauses are no longer supported in a primary key, unique key, or foreign key (new) constraint definition. Use the CREATE INDEX statement in ElevateDB to create an index with custom column sorting. The COMPRESS clause is no longer supported in a primary key, unique key, or foreign key (new) constraint definition. ElevateDB performs automatic index compression as necessary. The TEXT INDEX, STOP WORDS, SPACE CHARS, and INCLUDE CHARS clauses are no longer necessary. Use the CREATE TEXT INDEX statement in ElevateDB to create a new text index. The LOCALE clause is no longer necessary. ElevateDB supports column-level collations. Please see the Internationalization topic for more information. The WITH clause of the ENCRYPTED clause is no longer necessary. ElevateDB uses one encryption password per application for all encryption, and it is represented by the EncryptionPassword property. Also, the ENCRYPTED clause now resides after the VERSION clause (see next item). The USER MAJOR VERSION and USER MINOR VERSION clauses have been combined into one VERSION clause that accepts a NUMERIC value with a scale of 2. Also, the VERSION clause now resides after the DESCRIPTION clause. The LAST AUTOINC clause is no longer necessary. The seed and increment values for IDENTITY columns can be specified in the column definitions. |
CREATE INDEX | The IF NOT EXISTS clause is no longer supported. ElevateDB uses catalog queries to determine if an index exists. Please see the System Information topic for more information. The UNIQUE clause is no longer supported. ElevateDB requires that unique keys constraints be defined using a constraint definition in a CREATE TABLE or ALTER TABLE statement. The NOCASE clause is no longer necessary in an index definition. ElevateDB uses the collation defined for the column in the column definition for determining the default collation for the indexed columns, and also allows for the COLLATE clause to be used in the index definition in order to override the default column collation. Please see the Internationalization topic for more information. The COMPRESS clause is no longer supported in an index definition. ElevateDB performs automatic index compression as necessary. |
ALTER TABLE | The IF EXISTS clause is no longer supported. ElevateDB uses catalog queries to determine if a table exists. Please see the System Information topic for more information. The IF EXISTS and IF NOT EXISTS clauses are no longer supported for column definitions. ElevateDB uses catalog queries to determine if a table column exists. Please see the System Information topic for more information. The REDEFINE clause is no longer supported for column definitions. In order to redefine a column using the same column name, use the ALTER AS clause (see next). In order to rename a column, use the RENAME clause. The ALTER clause is new for column definitions. This clause allows you to alter the DEFAULT expression, drop the default expression, change the DESCRIPTION of the column, move the column to a new position in the table using the MOVE TO clause, or alter the entire column definition using the AS clause. The column definition AT clause has been moved to the end of the column definition. The column definition NULLABLE clause is no longer supported. To make a column nullable in ElevateDB, don't include the NOT NULL clause. The column definition DEFAULT clause accepts any basic expression in ElevateDB. A column definition may now include a GENERATED clause to specify that the column is a generated column. Generated columns can be generated as sequence numbers or expressions. The column definition MIN and MAX clauses are no longer necessary. ElevateDB supports column constraints via the CHECK clause. ElevateDB allows for specifying primary key, unique key, and foreign key constraints in a column definition. The CHARCASE clause is no longer supported. The COMPRESS clause has been renamed to COMPRESSION and moved so that it is next to the data type definition. The REDEFINE clause is no longer supported for constraint definitions. Use the RENAME clause to rename a constraint. The NOCASE clause is no longer necessary in a primary key, unique key, or foreign key (new) constraint definition. ElevateDB uses the collation defined for the column in the column definition for determining the collation of these types of constraints. Please see the Internationalization topic for more information. The DESC and ASC clauses are no longer supported in a primary key, unique key, or foreign key (new) constraint definition. Use the CREATE INDEX statement in ElevateDB to create an index with custom column sorting. The COMPRESS clause is no longer supported in a primary key, unique key, or foreign key (new) constraint definition. ElevateDB performs automatic index compression as necessary. The TEXT INDEX, STOP WORDS, SPACE CHARS, and INCLUDE CHARS clauses are no longer necessary. Use the CREATE TEXT INDEX statement in ElevateDB to create a new text index. The LOCALE clause is no longer necessary. ElevateDB supports column-level collations. Please see the Internationalization topic for more information. The WITH clause of the ENCRYPTED clause is no longer necessary. ElevateDB uses one encryption password per application for all encryption, and it is represented by the EncryptionPassword property. Also, the ENCRYPTED clause now resides after the VERSION clause (see next item). The USER MAJOR VERSION and USER MINOR VERSION clauses have been combined into one VERSION clause that accepts a NUMERIC value with a scale of 2. Also, the VERSION clause now resides after the DESCRIPTION clause. The LAST AUTOINC clause is no longer necessary. The seed and increment values for IDENTITY columns can be specified in the column definitions. The NOBACKUP clause has been renamed to the NO BACKUP FILES clause. |
DROP TABLE | The IF EXISTS clause is no longer supported. ElevateDB uses catalog queries to determine if a table exists. Please see the System Information topic for more information. |
DROP INDEX | The IF EXISTS clause is no longer supported. ElevateDB uses catalog queries to determine if an index exists. Please see the System Information topic for more information. The PRIMARY clause is no longer supported. ElevateDB does not allow a primary key to be dropped using the DROP INDEX statement. Instead, you must use the ALTER TABLE statement to add or drop constraints for a table. |
IMPORT TABLE | The IF EXISTS clause is no longer supported. ElevateDB uses catalog queries to determine if a table exists. Please see the System Information topic for more information. The COLUMNS clause has been renamed and the COLUMN portion has been dropped, retaining only the columns list in parentheses. Also, the clause has been moved so that it is right after the import file name. The DELIMITER clause has been renamed to DELIMITER CHAR. The QUOTE CHAR clause has been added to allow you to specify the quote character to be used for string values. The DATE clause has been renamed to the DATE FORMAT clause. The TIME clause has been renamed to the TIME FORMAT clause. The DECIMAL clause has been renamed to the DECIMAL CHAR clause. The BOOLEAN clause has been added to allow you to specify the literals used for True and False, respectively. The WITH HEADERS clause has been renamed to the USE HEADERS clause and has been moved to right after the BOOLEAN clause. The MAX ROWS clause has been added to allow you to specify the maximum number of rows that should be imported from the file. |
EXPORT TABLE | The IF EXISTS clause is no longer supported. ElevateDB uses catalog queries to determine if a table exists. Please see the System Information topic for more information. The COLUMNS clause has been renamed and the COLUMN portion has been dropped, retaining only the columns list in parentheses. Also, the clause has been moved so that it is right after the export file name. The DELIMITER clause has been renamed to DELIMITER CHAR. The QUOTE CHAR clause has been added to allow you to specify the quote character to be used for string values. The DATE clause has been renamed to the DATE FORMAT clause. The TIME clause has been renamed to the TIME FORMAT clause. The DECIMAL clause has been renamed to the DECIMAL CHAR clause. The BOOLEAN clause has been added to allow you to specify the literals used for True and False, respectively. The WITH HEADERS clause has been renamed to the INCLUDE HEADERS clause and has been moved to right after the BOOLEAN clause. The MAX ROWS clause has been added to allow you to specify the maximum number of rows that should be exported to the file. |
OPTIMIZE TABLE | The IF EXISTS clause is no longer supported. ElevateDB uses catalog queries to determine if a table exists. Please see the System Information topic for more information. The ON clause has been renamed to the USING INDEX clause. The NOBACKUP clause has been renamed to the NO BACKUP FILES clause. |
REPAIR TABLE | The IF EXISTS clause is no longer supported. ElevateDB uses catalog queries to determine if a table exists. Please see the System Information topic for more information. The FORCEINDEXREBUILD clause is no longer supported. |
New | Description |
CREATE DATABASE | Creates a new database. |
ALTER DATABASE | Alters an existing database. |
DROP DATABASE | Drops an existing database. |
RENAME DATABASE | Renames an existing database. |
CREATE STORE | Creates a new file store. |
ALTER STORE | Alters an existing file store. |
DROP STORE | Drops an existing file store. |
RENAME STORE | Renames an existing file store. |
CREATE USER | Creates a new user. |
ALTER USER | Alters an existing user. |
DROP USER | Drops an existing user. |
RENAME USER | Renames an existing user. |
CREATE ROLE | Creates a new role. |
ALTER ROLE | Alters an existing role. |
DROP ROLE | Drops an existing role. |
RENAME ROLE | Renames an existing role. |
GRANT PRIVILEGES | Grants privileges to an existing user or role on a specified object. |
REVOKE PRIVILEGES | Revokes privileges for an existing user or role from an existing object. |
GRANT ROLES | Grants roles to an existing user. |
REVOKE ROLES | Revokes roles from an existing user. |
CREATE JOB | Creates a new job. |
ALTER JOB | Alters an existing job. |
DROP JOB | Drops an existing job. |
RENAME JOB | Renames an existing job. |
CREATE MODULE | Creates (registers) a new external module. |
ALTER MODULE | Alters an existing external module. |
DROP MODULE | Drops an existing external module. |
RENAME MODULE | Renames an existing external module. |
CREATE TEXT FILTER | Creates a new text filter. |
ALTER TEXT FILTER | Alters an existing text filter. |
DROP TEXT FILTER | Drops an existing text filter. |
RENAME TEXT FILTER | Renames an existing text filter. |
CREATE WORD GENERATOR | Creates a new word generator. |
ALTER WORD GENERATOR | Alters an existing word generator. |
DROP WORD GENERATOR | Drops an existing word generator. |
RENAME WORD GENERATOR | Renames an existing word generator. |
CREATE MIGRATOR | Creates a new database migrator. |
ALTER MIGRATOR | Alters an existing database migrator. |
DROP MIGRATOR | Drops an existing database migrator. |
RENAME MIGRATOR | Renames an existing database migrator. |
CREATE TRIGGER | Creates a new trigger on an existing table. |
ALTER TRIGGER | Alters an existing trigger. |
DROP TRIGGER | Drops an existing trigger from a table. |
RENAME TRIGGER | Renames an existing trigger on a table. |
CREATE TEXT INDEX | Creates a new text index on an existing table. |
ALTER INDEX | Alters an existing index. |
CREATE VIEW | Creates a new view. |
ALTER VIEW | Alters an existing view. |
DROP VIEW | Drops an existing view. |
RENAME VIEW | Renames an existing view. |
CREATE FUNCTION | Creates a new function. |
ALTER FUNCTION | Alters an existing function. |
DROP FUNCTION | Drops an existing function. |
RENAME FUNCTION | Renames an existing function. |
CREATE PROCEDURE | Creates a new procedure. |
ALTER PROCEDURE | Alters an existing procedure. |
DROP PROCEDURE | Drops an existing procedure. |
RENAME PROCEDURE | Renames an existing procedure. |
SET BACKUPS STORE | Sets the current backups store for ElevateDB. |
BACKUP DATABASE | Backs up an existing database. |
RESTORE DATABASE | Restores a database from a backup. |
PUBLISH DATABASE | Publishes an existing database. |
UNPUBLISH DATABASE | Unpublishes a database. |
SET UPDATES STORE | Sets the current updates store for ElevateDB. |
SAVE UPDATES | Saves all logged updates to published tables in an existing database. |
LOAD UPDATES | Loads logged updates from an update file into an existing database. |
COPY FILE | Copies a file in a store to a new file name, and optionally, store. |
RENAME FILE | Renames a file in a store to a new file name. |
DELETE FILE | Deletes a file in a store. |
SET FILES STORE | Sets the current files store for ElevateDB. |
DISCONNECT SERVER SESSION | Disconnects a server session on an ElevateDB Server. |
REMOVE SERVER SESSION | Removes a server session from an ElevateDB Server. |
This web page was last updated on Thursday, November 16, 2023 at 10:39 AM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |