Cross Platform Compatability Guide

Top  Previous  Next

 

 

Design Compatibility Matrix

 

This table shows what combinations are available for the design stage of creating your web site.

 

Work Station

Scripting

Database connection

Databases

X-Gen to

Windows

ASP

ADO

MS Access, MS SQL Server and all ADO compliant Databases

Windows: All
Unix: PHP/mySQL


ASP

ODBC

mySQL and all ODBC compliant Databases

Windows: All
Unix:  PHP/mySQL


PHP

ODBC

All ODBC Compliant Databases

Windows All
Unix: PHP/mySQL

 

 

Publishing Compatibility Matrix

 

This table shows what scripting languages and database technologies mixes are supported when you publish to your host.

 

Server

Scripting

Database connection

Databases

Unix

PHP

MySQL (native)

mySQL

Windows

ASP

ADO

MS Access, MS SQL Server, all other OLEDB  compliant databases


ASP

ODBC

MS Access, MS SQL Server, All other ODBC Compliant Databases


PHP

ODBC

All ODBC Compliant databases


PHP

MySQL (Native)

mySQL

 

Database Compatibility Matrix

 

This table shows the level of compatibility for database objects that you need between your design database and your target database.

 

Data Base  Object

Target Requirement

Comment

Table Names

Identical Name

Target database names must match EXACTLY to the design database.  Some databases may be case sensitive

Column Names

Identical Name

Same as above.

Tables

All Referenced

All tables referenced in the design must be on the target.  Tables not used in the design do not need to be on the target. (note that pick lists and other functions may implicitly reference tables)

Columns

All Referenced

All columns referenced in design must be on the target.  Columns not referenced in the design can be omitted on the target.

Identifiers

Identical

All identifiers in referenced tables must be identical.

Data types

Compatible

Target data types must be compatible with source.  For example dates on the source must be dates on the target.

Stored Procedures

None

Stored procedures are not used by dbQwikSite code and are not required unless for other reasons.

Database Users

None

Database users can be different.

Indexes

Limited

Primary indexes (identifiers) must be the same on both source and target. Other indexes can vary, as indexes are not explicitly referenced.

Database name

None

Database names can be different. (not the names of objects in your database)

Constraints

None

SQL statements will be subject to any constraints that you implement in your database.

Triggers

None

No requirement in dbQwikSite code.

Optionally

None

Column optionally can differ however