Levelset v4.0.8 (September 30,
2007) |
- Changed references from Canam to Turbo Computer Systems, Inc.
|
Levelset
v4.0.7 (December 5, 2006) |
- Various improvements to user interface.
- Many trial users found the 10 record limit on the Light version too restricting to give TurboData a good test. Changed the limitation from 10 rows of data per table to 100 rows.
|
Levelset
v4.0.6 (September 9, 2005) |
- Generate GUIDs
Added more ADO options to DB Connection Advanced Tab
such as Mode, Lock Type, Cursor Type etc.
- Other data source - New feature to map all matching
columns in a table
- Insert SQL - Add statements before and after a
table, such as IDENTITY_INSERT ON tablename
- Select Max Id from target DB when generating
data.
- Update Column Generation rules - removing the
ending range for a particular column gave a type
mismatch error.
- Automatically update all DB connections to an
other DB in a scenario.
- Read new Oracle database schema - Filter on owner
when reading in tables.
- Fail to read in new database schema would give
meaningful message on first attempt such as "Invalid
user id and password" but the second attempt
would give error 3420 (Object invalid or no longer
set.)
- Give message if FK's parent ID is excluded. Do
not let user exclude a parent ID, or set a child
FK if parent ID is excluded.
- Unique FKs - Make sure that FK values are unique
for each set of child data generated for it's parent.
|
Levelset
v4.0.5 (February 7, 2005) |
- Enabled client/server licensing for companies with
bulk orders of TurboData.
- Reading data from Other DB - Give user option to ignore
Owner of the Table. This was causing problems with
MS/SQL Server.
- Other DB - If no tables found then give message (and
don't cause an error when refresh is pressed.).
- View data on other DB - Read table names from physical database connection
.
|
Levelset
v4.0.4 (October 20, 2004) |
- Oracle 9i was not reading in Nullable property correctly
when using an ODBC DAO connection.
- Oracle 9i was not saving columns in correct sort order
when using an ODBC DAO connection.
- Fixed bug that occurred when using DAO ODBC connection
to read a value from an Other DB.
- If reading a value form an Other DB fails, there is
now an option to view the generated Select SQL statement.
- Improved registration component.
- Data Composer component was not creating all the attributes
correctly when reading in a Report Composer File Reader.
- Data Composer component now has integration with AllFusion
Gen.
- When running Data Composer as a Gen plug in, it will
now prompt the user what to do first. Either open
an existing model, or read in a new model.
|
Levelset
v4.0.3 (June 4, 2004) |
- Added Create Table DDL generation for DB2 and MS SQL
Server.
- ADO connection option to choose cursor location.
- SQL Errors that occur during data generation can now
be copied to the clipboard so that they can easily
be emailed to TurboData support.
- Copy generation rules to all columns with the same
data type, not just those with the same properties,
such as length.
- After generating data for a scenario, save the last
used generation settings such as DBMS and output text
file name.
- Do not allow invalid characters in test scenarion
name.
- Changed error message "Please install Microsoft
Jet 4 Service Pack 3." to "Please install
the latest Microsoft Jet 4 Service Pack."
- Changed error message "please also install Microsoft
Data Access Components (MDAC) v2.5" to "please
also install the lastest Microsoft Data Access Components
(MDAC)"
- View Data - When selecting the View Table option,
automatically read the data from the selected table.
This saves the user 1 click.
- Right clicking on main toolbar showed a toolbar called
Test.
- Alternate Data Source - Read Interval and Hold Frequency
now hold up to 4 digits.
- Detect Personal License on restricted functions.
- Options - Start date minimum year changed to 1601.
- Time controls were showing dates on the drop down.
- Data Generator - Feature to trim leading and trailing
spaces from generated data.
- Data Generator - MS SQL Server add square brackets
to table and column names.
|
Levelset
v4.0.2 (March 2, 2004) |
|
- Option to skip comments from output SQL file (Professional
version only).
- Option to pre-select Tables to read in to TD. Read tables
only if the table name is in the "tables to read"
file.
- Option to compress TurboData.MDB file and TurboData
Values.MDB file.
- SQL Builder - New Button to link to the window to view
and edit data in a grid.
- Fixed Scale and Precision confusion. Precision is the
number of digits in a number. Scale is the number of
digits to the right of the decimal point in a number.
For example, the number 123.45 has a precision of 5
and a scale of 2.
- Grid View of Data - Only list tables read into the TurboData
schema as opposed to all tables in the physical database.
- Escape Key to Cancel a process - When Escape key is
pressed, TurboData will now ask for confirmation before
cancelling the process.
- Do not error when trying to resolve a foreign key who's
parent column has been excluded.
- Display scenarios on main window sorted by name.
- Reading in Excel spreadsheet from an invalid row and
column gave run time error 1004: Object doesn't support
this property or method. This error is now trapped and
handled.
- Reading in Excel spreadsheet - give user friendly message
when end of data token has been reached.
- Revoke option for Professional version.
- Data Composer version can now be registered online.
|
Levelset
v4.0.1 (January 19, 2004) |
- Create Table DDL for MySQL.
- Don't allow 2 scenarios to have the same name.
- Edit Database - Show Sort Order Column
- Edit Database - Add Sort Columns Button
- Fixed bug in setting the sort order of columns to generate.
- Edit scenario - sometimes moving a table down in the
tree didn't work correctly.
- Do not show columns in bold unless scenario is Update
or Insert.
|
Levelset
v4.0.0 (December 17, 2003)
|
- Generate values with dependencies, eg City within
a Country.
- Random character or digit fill.
- Edit Scenario - If column has generation rules show
it in bold.
- Edit Scenario - If column is excluded show it in italics.
- Edit Scenario - If column is a foreign key show it in
red.
- Edit Scenario - If column is a foreign key that is resolved
by a parent show it in bold.
- Use VBScripting technology for maximum date generation
flexibility
- Read value from Other DB - null value will now return
empty string.
- If a scenario folder has been physically deleted
byuser suppress errors given on Rename Scenario and
Generate Data.
- Set a default for a column using data from another database.
Select that table for data generation gave error "Run
time Error 3021, No Current Record".
- Set a defaults for a column. Select that table for data
generation. Defaults for column start range, end range
and quote override were not being copied.
- Generic Values - New button to TRIM all values in the
repository. This will remove any preceding and trailing
spaces from the values to stop the test data generator
inserting unecessary space characters in the database.
For example 'John ' will be trimmed to 'John'. Next
release of TurboData will be distributed with the generic
values already trimmed.
- Generic Values - Sorting the values changes the mouse
pointer to an hour glass, and displays the total number
of values processed.
- Edit Scenario - New option to copy column generation
rules to make the default table/column.
- Edit Scenario - New option to copy column generation
rules to all tables/column rules of the same data type
and column name containing defined search text.
- Generate Data - An excluded column with 'Unique' setting
was having values assigned to it behind the scenes even
though the values were not used in the final generated
data. If not enough unique values were available it
- would stop the generation.
- Edit Scenario - New button to Include all columns for
a selected table.
- Edit Scenario - New button to Exclude all columns for
a selected table.
- Added Generic Value of Random Characters, length 1.
- If user selects a Generic Value Category of 'Date' or
'Time' datatype for a Column with a 'Timestamp' datatype
it will prompt to automatically set the Data Format
edit pattern appropriately so those generic values can
be used for the timestamp column.
- Generate a set of multiple scenarios in a batch run.
- Data generation - combine values, eg use First Name
and Last Name in a column called Full Name.
Edit Scenario - Update a Value Source on a selected
column that is not in view, will now update the value
node without having to close and open the scenario.
- Edit Scenario - To remove constant datetime value you
do not need to manually select the "Use Generated
Data" combo before clicking on the "Derived
by TurboData" option.
- Edit Scenario - Moving a resolved foreign key column
gave an error.
- Edit Scenario - Clear Generation Rules
- Options, Editor - Launch Editor: Executable name and
folder should be enclosed in double quotes
- Options, Editor - Launch Editor: File name and folder
should be enclosed in double quotes
- SQL92 syntax (can be used by JDBC)
- Handle Oracle 9i data type of "TIMESTAMP(6) WITH
LOCAL TIME ZONE" without crashing. If datatype
contains the string "timestamp" TurboData
will treat this column as a timestamp. (It can be manually
overridden to Time or Date if that is more suitable
for the target DBMS.)
- Set FKs - If no tables are in the scenario, the
button "Automatically Set Remaining Foreign Keys"should
be disabled.
- Edit Scenario - If multiple columns are selected, disable
Include/Exclude options.
- If generated data uses default date/time because of
unexpected input format, display a message explaining
this to the user.
- Some versions of Oracle were not reading in the foreign
keys. Try more than one method of reading in foreign
keys if first attempt doesn't work.
- Data generation - MS/SQL Server times and timestamps
now include seconds.
Levelset v3 Archive
|