MySQL Databases (Magic xpa 4.x)
The following topics describe Magic xpa’s functionality when working with MySQL:
MySQL Data Types
Magic xpa Data Types - MySQL
Database Information
The following is information about working with the MySQL database:
|
Locking
|
No explicit table locks exist in MySQL. Therefore, Share-None and Share-Read have no effect. The underlying database engine itself executes the locking.
|
|
Physical Locking
|
A physical lock is a method that ensures that no one else can modify a record that is currently locked. Specifically, from the moment a user locks the record until that user releases the record, the record cannot be modified by another user. The physical lock is implemented as follows: When Magic xpa locks a record according to its locking strategy, Magic xpa issues a Select statement with a FOR UPDATE clause.
The FOR UPDATE clause prevents other applications from making changes to the record until the end of the transaction.
Since version: 4.6
|
|
Views
|
You must define a virtual unique index for a View. Insert, Update, and Delete operations are permitted on Views. Magic xpa will display an error message and will not convert or rename the View in the database.
|
|
Direct SQL
|
MySQL cannot be the Result Database in Direct SQL tasks.
|
|
|
The Magic xpa Single User Edition does not support MySQL database.
|
