Using SQL Databases from APL (Dyalog & other)
Overview
My Background
SQL Work at STSC
STSC, Manugistics, and Later
SQL Concepts You Must Know
SQL Has DML and DDL
SQL Concepts You Must Know
Client / Server Concepts
One Program Touches the Data
Let the Server Do the Work
Avoid “Chatty” Programs
SQL Concepts You Must Know
Use Null Values Sparingly
SQL Concepts You Must Know
All SQL Data is in Tables
SQL Columns
Column Names
SQL Concepts You Must Know
Numbers
Strings
Dates and Times
Time Intervals
Binary
Boolean
SQL Concepts You Must Know
How Relationships Work in SQL
SQL Table Design
Relationships – many to many
More SQL Design Thoughts
More Tables Are Often Better
Historical Data
SQL Joins
Relationships vs. Join Types
SQL Databases are Standard
Database Transactions
Security Built In
Advanced DBMS Features
Database Indexes
Database Views
SQL Subqueries
Stored Procedures and Triggers
Support for XML Data
Partitioned Tables
Materialized Views
A Quick Look at Implementation
Which database to choose?
Can You Choose?
What’s Most Important?
What’s Most Important?
Lesser-known Products
APL-based or APL-aware?
APL Can Speak to SQL Easily
SQAPL Wins
Other Choices Are Inferior
SQAPL Sets
Basics of Using Sets
How Do Sets Work?
More Possible Enhancements
Database-Specific Tools
Improving SQAPL’s API
Performance Issues
Figuring Out What’s Wrong
Metadata Based Tools
Other Tools
Lessons Learned
More Lessons
Unproven (by me) Ideas
Model Definition is Often Hazy
Problems Caused by UI Models
Use Model Code in the UI
UI / Data Model Separation
UI Forms Reference a Model
Writing Models
A Big Thank You to Morten
Скачать презентацию Using SQL Databases from APL Dyalog other
45c2379b29810c113c2db3f8139add13.ppt