Chat now with support
Chat with Support

Toad Data Modeler 6.2 - User Guide

Introduction User Interface Models and Model Objects
Physical Data Model
About Physical Data Modeling Benefits of Physical Data Model Entity Relationship Diagram Objects Basic Database Design Advanced Database Design
Universal Data Model Logical Data Model Working with Model Objects Model Properties Model Statistics
Features and Tools
Application Variables Export/Import DDL Script Generation Graphics Model Actions Print Projects Reports Reverse Engineering Scripting and Customization SQL Templates Tips and Tricks Toad for Oracle Integration Toad Intelligence Central (TIC) Integration Tools Version Control
Options and Configuration Databases
Supported Databases Connection Types by Database DB2 UDB v. 8 (LUW) DB2 v. 9 (LUW) DB2 v. 9.5 (LUW) DB2 v. 9.7 (LUW) DB2 v. 10.1 (LUW) DB2 v. 10.5 (LUW) DB2 z/OS v. 9 DB2 z/OS v.10 DB2 z/OS v. 11 Greenplum 4.1 Greenplum 4.2 Ingres 9.3 Ingres 10.0 Microsoft Access 2000/2002/2003 Microsoft Access 2007/2010 Microsoft Azure SQL Database Microsoft Azure SQL Database V12 Microsoft SQL Server 2000 Microsoft SQL Server 2005 Microsoft SQL Server 2008 Microsoft SQL Server 2012 Microsoft SQL Server 2014 Microsoft SQL Server 2016 MySQL 5.0 MySQL 5.1 MySQL 5.5 MySQL 5.6 MySQL 5.7 Oracle 9i Oracle 10g Oracle 11g Release 1 Oracle 11g Release 2 Oracle 12c Release 1 Oracle 12c Release 2 PostgreSQL 8.1 PostgreSQL 8.2 PostgreSQL 8.3 PostgreSQL 8.4 PostgreSQL 9.0 PostgreSQL 9.1 PostgreSQL 9.2 PostgreSQL 9.3 PostgreSQL 9.4 PostgreSQL 9.5 SQLite 3.7 Sybase ASE 12.5 Sybase ASE 15 Sybase ASE 15.5 Sybase ASE 15.7 SAP ASE 16.0 Sybase IQ 15.2 Sybase SQL Anywhere 11 SAP SQL Anywhere 17 Teradata 13 Vertica Database 8.0
Legal Information

SQLite 3.7

Reverse Engineering

Databases > SQLite 3.7 > Reverse Engineering

Available Data Providers are:

  • Native Connection

Native Connection:

Though SQLite database is case insensitive, Reverse Engineering in Toad Data Modeler is case sensitive. This leads to a problem that e.g. when a column name is "ATR" and an index is defined with column name "Atr", the names do not get paired and an error message is thrown.

If some object name includes UTF characters, then the object does not get loaded during Reverse Engineering.

Appropriate SQLite3.dll library is necessary for successful connection.

Note:

  1. On page Options, the Load Some Objects as SQL Sentence Only checkbox is applicable for Views, Triggers and Virtual Tables. If selected, triggers are loaded as they are saved in system table.
  2. During Reverse Engineering, objects from only one database are loaded. Therefore, database name is not loaded during Reverse Engineering.

Specifics

Databases > SQLite 3.7 > Specifics

Though SQLite database is case insensitive, Reverse Engineering in is case sensitive. This leads to a problem that e.g. when a column name is "ATR" and an index is defined with column name "Atr", the names do not get paired and an error message is thrown.

If some object name includes UTF characters, the object does not get loaded during Reverse Engineering.

Entity

Inner Scriptbox — e.g. for defining constraint in text. Code in Inner Script is generated in the body of CREATE TABLE command, at the end after all attributes and constraints. During reverse engineering, foreign key constraint definitions, which are not possible to visualize by relationship, are loaded here.

Attribute

Autoincrement— Data type must be set to INTEGER and the particular attribute must be in a single-attribute primary key. Note that in SQLite syntax, Autoincrement is defined as a part of a column constraint of a primary key statement but in Toad Data Modeler it is set directly in the Attribute.

Collation

3 built-in collating functions: BINARY, NOCASE, and RTRIM, defined in text in particular box. For keys and indexes you can define Collation for the selected item in Key/Index Properties dialog, Attributes/Items tab, in the Collation column (see the screenshots below.)

Relationship

Property MATCH is available in syntax but it is not used and therefore not supported in Toad Data Modeler.

Relationships can be defined only by CREATE TABLE command.

It is not possible to have relationships between entities from different databases.

If a foreign key is created, it can contain a reference to a non-existing table/name. During reverse engineering, thus foreign key is loaded in the Inner Script box of the particular entity.

Note: By default, foreign keys are not supported in SQLite; they can be created but are disabled. They can be enabled by command PRAGMA foreign_keys=ON;, but default value after SQLite start is OFF!

Key

New Conflict Resolution Algorithm box.

On tab Attributes, you can define Collation for the selected item in the Collation column.

Index

New If Not Exists checkbox.

On tab Items, you can define Collation for the selected item in the Collation column.

Trigger - Entity

New checkboxes Temporary Trigger and If Not Exists.

Trigger - View

View Trigger has Trigger Fire box disabled with INSTEAD OF set.

View

The content of a new Limit tab is generated in script only if Generate SQL Only and SELECT in Views as Text are not selected.

Virtual Table

During Reverse Engineering, virtual table is loaded as text - CREATE VIRTUAL TABLE.

Database

Database serves only for listing function. Available for Entity, View, Virtual Table. It denotes to which database the object belongs.

During reverse engineering, objects from only one database are loaded. Therefore, database name is not loaded during reverse engineering.

Script Generating

Databases > SQLite 3.7 > Script Generating

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating