Application scalability.
Multiple instances of your Iron Speed Designer-created applications can run on multiple
machines. Deploy your applications across Web farms with as many servers as you wish,
providing the scalability needed by most applications.
A typical dual processor Pentium IV
can handle approximately 250 simultaneous users running an application of average
complexity. However, you can greatly increase application performance by appropriate
database table indexing.
|
|
|
Multi-database applications.
Build applications of any size using multiple databases (multiple schemas in Oracle) and
an unlimited number of tables.
|
|
|
Database views.
You can perform nearly every operation on a database view that you can on a table.
Generate an entire suite of application pages based on database views, including
Add Record, Edit Record, Show Record, Show Table and Edit Table pages. Database views
are great for constructing complex dashboard pages. And, you can create Master-Detail
pages based on database views by defining Virtual Primary Keys and Virtual Foreign Keys
in Iron Speed Designer.
|
A set of table panels in the Alps design theme
|
|
Multi-table join queries.
Construct complex, multi-table join queries to display record and table data using your
database's underlying tables, database views, and named queries defined in Iron Speed Designer.
Queries can include calls to functions built into your application, custom code functions,
and system calls.
|
|
|
Inline SQL generation.
Iron Speed Designer automatically builds all the SQL statements required for each
database-connected form, Web page, table, and report in your application, as well
as all the database access logic and storage management code. You do not need
to know any SQL to build applications with Iron Speed Designer. Iron Speed Designer
creates SQL based on your data model and user interface design. A variety of
data filters and navigation components provide your end-users with additional
viewing and reporting flexibility.
|
|
Stored procedure generation.
Most of your application's SQL is placed in stored procedures, enhancing run-time
performance because the queries are stored and executed directly from the database. This
also minimizes the number of round-trips between the application program and the database,
further enhancing performance.
| Database |
Supported |
Microsoft SQL Server
(Transact-SQL) |
 |
| Oracle (PL/SQL) |
|
| Microsoft Access |
|
| MySQL |
|
|
|
Concurrency handling.
Implementing concurrency handling is typically very tedious and must be applied
carefully to nearly every transaction in an application. Iron Speed Designer
features optimistic concurrency handling* for each of your transactions so users
cannot unintentionally overwrite each other's changes.
*Concurrency handling is only available when generating stored procedures.
|
|
|
Transaction management.
Applications built with Iron Speed Designer use a "page-based" transaction model.
All of the changes made to any record on the current web page are submitted when the
user clicks "OK" (or takes a similar action on the page). A single "commit"
concludes the transaction. Iron Speed Designer uses stored procedures to ensure that
database updates - record add, edit, delete and import - are of maximum efficiency and
require only one round-trip to the database.
|
|
Virtual foreign keys.
You can inform Iron Speed Designer of virtual, or "implicit", foreign key relationships
between your database tables and database views that are not be defined in the database.
Iron Speed Designer does the rest, helping you build the appropriate application web pages
and SQL queries, treating these Virtual Foreign Keys as if they existed in the database.
Iron Speed Designer understands your database may not be perfectly structured, and
Virtual Foreign Keys are a great way to help you build real-world applications.
|
|
|
Virtual primary keys.
For database tables that do not have explicit primary keys, you can now specify the
primary key relationships in Iron Speed Designer, allowing you to create Add Record,
Edit Record and Show Record pages for these tables. You don’t have to change
your database schema in order to generate full-featured applications.
|
|
