|
<< Click to Display Table of Contents >> SQL scripts |
  
|
|
<< Click to Display Table of Contents >> SQL scripts |
|
As a specially designed feature PdxEditor also handles processing of standard SQL scripts including mixed DDL and DML statements usually not processed within BDE Paradox or dBASE applications.
This way populating tables is easily performed with well formatted mixed SQL CREATE and INSERT scripts.
The feature is dependent on semicolon [;] separation of included SQL statements and will disregard
/* properly delimited SQL comments */.
As an off BDE standard PdxEditor also features handling -- SQL single line comments.
Interpreting and parsing is based on the semicolons as statement terminators, and semicolons are thus not accepted within statements except as parts of properly delimited comments.
Do notice, that creating tables will have to comply with the BDE rules for field names with spaces or special characters as e.g.
CREATE TABLE Orders (
Orders."First Name" CHAR (25)
, Orders."Last Name" CHAR(30)
, Status SMALLINT
, Orders."Zip Code" CHAR(30));
as well as the BDE often does not accept local date formats nor the date ISO format, but usually (always?) accepts the US format MM/dd/yyyy, which is best used for inserting data whatever the locale system setting.
Finally decimal character for INSERT statements is always dot [.] even if comma is the system setting.
As SQL TRANSACTION (and thus ROLL BACK) is not supported by the BDE engine, care should be taken when executing extensive updating scripts.
It is thus recommended to make copies of target tables enabling you to revert changes before executing non proven SQL scripts.
Processing has been with from 60 to 100 INSERT statements per second as tested on various older PC's including Intel Core i5 2400S 2.5 GHz.
Testing on PC with a SSD has not revealed any speed advantage.
PdxEditor handles SQL scripts/SQL batches by first analysing the script for multi line and single line comments, which are cleared from the script, and then according to the remaining semicolon separators, parsing the script into individual SQL statements.
These statements are then automatically executed in sequence.
To comply with the issues of inside comments semicolons as in
/* DROP TABLE MyTable; */
SELECT * FROM OtherTable;
PdxEditor does always pre-process scripts before parsing.
__________________________