2003-10-19 21:05:23 +02:00
< html >
2004-03-15 23:17:52 +01:00
< head >
< title > ADODB Data Dictionary Manual< / title >
< meta http-equiv = "Content-Type" content = "text/html; charset=iso-8859-1" >
< style type = "text/css" >
body, td {
/*font-family: Arial, Helvetica, sans-serif;*/
font-size: 11pt;
}
pre {
font-size: 9pt;
}
.toplink {
font-size: 8pt;
}
< / style >
< / head >
< body bgcolor = "#FFFFFF" >
2003-10-19 21:05:23 +02:00
< h2 > ADOdb Data Dictionary Library for PHP< / h2 >
2004-07-10 09:19:40 +02:00
< p > V4.50 6 July 2004 (c) 2000-2004 John Lim (< a href = "mailto:jlim#natsoft.com.my" > jlim#natsoft.com.my< / a > ).< br > AXMLS (c) 2004 ars Cognita, Inc< / p >
2004-03-15 23:17:52 +01:00
< p > < font size = "1" > This software is dual licensed using BSD-Style and LGPL. This means you can use it in compiled proprietary and commercial products.< / font > < / p >
2004-07-10 09:19:40 +02:00
< table border = 1 > < tr > < td > < font color = red > Kindly note that the ADOdb home page has moved to < a href = http://adodb.sourceforge.net/ > http://adodb.sourceforge.net/< / a > because of the persistent
unreliability of http://php.weblogs.com. < b > Please change your links< / b > !< / font > < / td > < / tr > < / table >
< p > Useful ADOdb links: < a href = http://adodb.sourceforge.net/#download > Download< / a > < a href = http://adodb.sourceforge.net/#docs > Other Docs< / a >
2004-03-15 23:17:52 +01:00
< p > This documentation describes a PHP class library to automate the creation of tables,
indexes and foreign key constraints portably for multiple databases. Richard Tango-Lowy and Dan Cech
have been kind enough to contribute < a href = #xmlschema > AXMLS< / a > , an XML schema system for defining databases.< / p >
< p > Currently the following databases are supported:< / p >
< p >
< b > Well-tested:< / b > PostgreSQL, MySQL, Oracle, MSSQL.< br / >
< b > Beta-quality:< / b > DB2, Informix, Sybase, Interbase, Firebird.< br / >
< b > Alpha-quality:< / b > MS Access (does not support DEFAULT values) and generic ODBC.
< / p >
2003-10-19 21:05:23 +02:00
< h3 > Example Usage< / h3 >
2004-03-15 23:17:52 +01:00
< pre >
include_once('adodb.inc.php');
< font color = "#006600" > # First create a normal connection< / font >
$db->NewADOConnection('mysql');
$db->Connect(...);
< font color = "#006600" > # Then create a data dictionary object, using this connection< / font >
$dict = < strong > NewDataDictionary< / strong > ($db);
< font color = "#006600" > # We have a portable declarative data dictionary format in ADOdb, similar to SQL.
# Field types use 1 character codes, and fields are separated by commas.
# The following example creates three fields: "col1", "col2" and "col3":< / font >
$flds = "
< font color = "#663300" > < strong > col1 C(32) NOTNULL DEFAULT 'abc',
col2 I DEFAULT 0,
col3 N(12.2)< / strong > < / font >
";
< font color = "#006600" > # We demonstrate creating tables and indexes< / font >
$sqlarray = $dict->< strong > CreateTableSQL< / strong > ($tabname, $flds, $taboptarray);
$dict->< strong > ExecuteSQLArray< / strong > ($sqlarray);< br >
$idxflds = 'co11, col2';
$sqlarray = $dict->< strong > CreateIndexSQL< / strong > ($idxname, $tabname, $idxflds);
$dict->< strong > ExecuteSQLArray< / strong > ($sqlarray);
2003-10-19 21:05:23 +02:00
< / pre >
2004-03-15 23:17:52 +01:00
2003-10-19 21:05:23 +02:00
< h3 > Functions< / h3 >
2004-03-15 23:17:52 +01:00
< h4 > function CreateDatabase($dbname, $optionsarray=false)< / h4 >
< p > Create a database with the name $dbname;< / p >
< h4 > function CreateTableSQL($tabname, $fldarray, $taboptarray=false)< / h4 >
2003-10-19 21:05:23 +02:00
< pre >
2004-03-15 23:17:52 +01:00
RETURNS: an array of strings, the sql to be executed, or false
$tabname: name of table
$fldarray: string (or array) containing field info
$taboptarray: array containing table options
2003-10-19 21:05:23 +02:00
< / pre >
2004-03-15 23:17:52 +01:00
< p > The new format of $fldarray uses a free text format, where each field is comma-delimited.
The first token for each field is the field name, followed by the type and optional
field size. Then optional keywords in $otheroptions:< / p >
< pre > "$fieldname $type $colsize $otheroptions"< / pre >
< p > The older (and still supported) format of $fldarray is a 2-dimensional array, where each row in the 1st dimension represents one field. Each row has this format:< / p >
< pre > array($fieldname, $type, [,$colsize] [,$otheroptions]*)< / pre >
< p > The first 2 fields must be the field name and the field type. The field type can be a portable type codes or the actual type for that database.< / p >
< p > Legal portable type codes include:< / p >
2003-10-19 21:05:23 +02:00
< pre >
2004-03-15 23:17:52 +01:00
C: varchar
X: Largest varchar size
XL: For Oracle, returns CLOB, otherwise same as 'X' above
C2: Multibyte varchar
X2: Multibyte varchar (largest size)
B: BLOB (binary large object)
D: Date (some databases do not support this, and we return a datetime type)
T: Datetime or Timestamp
L: Integer field suitable for storing booleans (0 or 1)
I: Integer (mapped to I4)
I1: 1-byte integer
I2: 2-byte integer
I4: 4-byte integer
I8: 8-byte integer
F: Floating point number
N: Numeric or decimal number
2003-10-19 21:05:23 +02:00
< / pre >
2004-03-15 23:17:52 +01:00
< p > The $colsize field represents the size of the field. If a decimal number is used, then it is assumed that the number following the dot is the precision, so 6.2 means a number of size 6 digits and 2 decimal places. It is recommended that the default for number types be represented as a string to avoid any rounding errors.< / p >
< p > The $otheroptions include the following keywords (case-insensitive):< / p >
2003-10-19 21:05:23 +02:00
< pre >
2004-03-15 23:17:52 +01:00
AUTO For autoincrement number. Emulated with triggers if not available.
Sets NOTNULL also.
AUTOINCREMENT Same as auto.
KEY Primary key field. Sets NOTNULL also. Compound keys are supported.
PRIMARY Same as KEY.
DEF Synonym for DEFAULT for lazy typists.
DEFAULT The default value. Character strings are auto-quoted unless
the string begins and ends with spaces, eg ' SYSDATE '.
NOTNULL If field is not null.
DEFDATE Set default value to call function to get today's date.
DEFTIMESTAMP Set default to call function to get today's datetime.
NOQUOTE Prevents autoquoting of default string values.
CONSTRAINTS Additional constraints defined at the end of the field
definition.
2003-10-19 21:05:23 +02:00
< / pre >
2004-03-15 23:17:52 +01:00
< p > The Data Dictonary accepts two formats, the older array specification:< / p >
2003-10-19 21:05:23 +02:00
< pre >
2004-03-15 23:17:52 +01:00
$flds = array(
array('COLNAME', 'DECIMAL', '8.4', 'DEFAULT' => 0, 'NOTNULL'),
array('id', 'I' , 'AUTO'),
array('`MY DATE`', 'D' , 'DEFDATE'),
array('NAME', 'C' , '32', 'CONSTRAINTS' => 'FOREIGN KEY REFERENCES reftable')
);
2003-10-19 21:05:23 +02:00
< / pre >
2004-03-15 23:17:52 +01:00
< p > Or the simpler declarative format:< / p >
< pre >
$flds = "< font color = "#660000" > < strong >
COLNAME DECIMAL(8.4) DEFAULT 0 NOTNULL,
id I AUTO,
`MY DATE` D DEFDATE,
NAME C(32) CONSTRAINTS 'FOREIGN KEY REFERENCES reftable'< / strong > < / font >
";
< / pre >
2004-07-10 09:19:40 +02:00
< p > Note that if you have special characters in the field name (e.g. My Date), you should enclose it in back-quotes. Normally field names are not case-sensitive, but if you enclose it in back-quotes, some databases will treat the names as case-sensitive (eg. Oracle) , and others won't. So be careful.< / p >
2004-03-15 23:17:52 +01:00
< p > The $taboptarray is the 3rd parameter of the CreateTableSQL function. This contains table specific settings. Legal keywords include:< / p >
2003-10-19 21:05:23 +02:00
< ul >
2004-03-15 23:17:52 +01:00
< li > < b > REPLACE< / b > < br / >
Indicates that the previous table definition should be removed (dropped)together with ALL data. See first example below.
< / li >
< li > < b > DROP< / b > < br / >
Drop table. Useful for removing unused tables.
< / li >
< li > < b > CONSTRAINTS< / b > < br / >
Define this as the key, with the constraint as the value. See the postgresql example below.
Additional constraints defined for the whole table. You will probably need to prefix this with a comma.
< / li >
2003-10-19 21:05:23 +02:00
< / ul >
2004-03-15 23:17:52 +01:00
< p > Database specific table options can be defined also using the name of the database type as the array key. In the following example, < em > create the table as ISAM with MySQL, and store the table in the " users" tablespace if using Oracle< / em > . And because we specified REPLACE, drop the table first.< / p >
< pre > $taboptarray = array('mysql' => 'TYPE=ISAM', 'oci8' => 'tablespace users', 'REPLACE');< / pre >
< p > You can also define foreignkey constraints. The following is syntax for postgresql:
< pre > $taboptarray = array('constraints' => ', FOREIGN KEY (col1) REFERENCES reftable (refcol)');< / pre >
< h4 > function DropTableSQL($tabname)< / h4 >
< p > Returns the SQL to drop the specified table.< / p >
< h4 > function ChangeTableSQL($tabname, $flds)< / h4 >
2003-10-19 21:05:23 +02:00
< p > Checks to see if table exists, if table does not exist, behaves like CreateTableSQL.
If table exists, generates appropriate ALTER TABLE MODIFY COLUMN commands if
2004-03-15 23:17:52 +01:00
field already exists, or ALTER TABLE ADD $column if field does not exist.< / p >
2003-10-19 21:05:23 +02:00
< p > The class must be connected to the database for ChangeTableSQL to detect the
2004-03-15 23:17:52 +01:00
existence of the table. Idea and code contributed by Florian Buzin.< / p >
< h4 > function CreateIndexSQL($idxname, $tabname, $flds, $idxoptarray=false)< / h4 >
< pre >
RETURNS: an array of strings, the sql to be executed, or false
$idxname: name of index
$tabname: name of table
$flds: list of fields as a comma delimited string or an array of strings
$idxoptarray: array of index creation options
< / pre >
< p > $idxoptarray is similar to $taboptarray in that index specific information can be embedded in the array. Other options include:< / p >
< pre >
CLUSTERED Create clustered index (only mssql)
BITMAP Create bitmap index (only oci8)
UNIQUE Make unique index
FULLTEXT Make fulltext index (only mysql)
HASH Create hash index (only postgres)
DROP Drop legacy index
< / pre >
< h4 > function DropIndexSQL ($idxname, $tabname = NULL)< / h4 >
< p > Returns the SQL to drop the specified index.< / p >
< h4 > function AddColumnSQL($tabname, $flds)< / h4 >
< p > Add one or more columns. Not guaranteed to work under all situations.< / p >
< h4 > function AlterColumnSQL($tabname, $flds)< / h4 >
< p > Warning, not all databases support this feature.< / p >
< h4 > function DropColumnSQL($tabname, $flds)< / h4 >
< p > Drop 1 or more columns.< / p >
< h4 > function SetSchema($schema)< / h4 >
< p > Set the schema.< / p >
< h4 > function & MetaTables()< / h4 >
< h4 > function & MetaColumns($tab, $upper=true, $schema=false)< / h4 >
< h4 > function & MetaPrimaryKeys($tab,$owner=false,$intkey=false)< / h4 >
< h4 > function & MetaIndexes($table, $primary = false, $owner = false)< / h4 >
< p > These functions are wrappers for the corresponding functions in the connection object. However, the table names will be autoquoted by the TableName function (see below) before being passed to the connection object.< / p >
< h4 > function NameQuote($name = NULL)< / h4 >
< p > If the provided name is quoted with backquotes (`) or contains special characters, returns the name quoted with the appropriate quote character, otherwise the name is returned unchanged.< / p >
< h4 > function TableName($name)< / h4 >
< p > The same as NameQuote, but will prepend the current schema if specified< / p >
< h4 > function MetaType($t,$len=-1,$fieldobj=false)< / h4 >
< h4 > function ActualType($meta)< / h4 >
< p > Convert between database-independent 'Meta' and database-specific 'Actual' type codes.< / p >
< h4 > function ExecuteSQLArray($sqlarray, $contOnError = true)< / h4 >
2003-10-19 21:05:23 +02:00
< pre >
2004-03-15 23:17:52 +01:00
RETURNS: 0 if failed, 1 if executed all but with errors, 2 if executed successfully
$sqlarray: an array of strings with sql code (no semicolon at the end of string)
$contOnError: if true, then continue executing even if error occurs
< / pre >
< p > Executes an array of SQL strings returned by CreateTableSQL or CreateIndexSQL.< / p >
< hr / >
< a name = xmlschema > < / a >
< h2 > ADOdb XML Schema (AXMLS)< / h2 >
< p > This is a class contributed by Richard Tango-Lowy and Dan Cech that allows the user to quickly
and easily build a database using the excellent ADODB database library and a simple XML formatted file.
You can < a href = http://sourceforge.net/projects/adodb-xmlschema/ > download the latest version of AXMLS here< / a > .< / p >
< h3 > Quick Start< / h3 >
< p > First, create an XML database schema. Let's call it "schema.xml:"< / p >
< pre >
< ?xml version="1.0"?>
< schema version=" 0.2" >
< table name="mytable">
< field name="row1" type="I">
< descr> An integer row that's a primary key and autoincrements< /descr>
< KEY/>
< AUTOINCREMENT/>
< /field>
< field name="row2" type="C" size="16">
< descr> A 16 character varchar row that can't be null< /descr>
< NOTNULL/>
< /field>
< index name=" myindex" >
< col> row1< /col>
< col> row2< /col>
< /index>
< /table>
< sql>
< descr> SQL to be executed only on specific platforms< /descr>
< query platform="postgres|postgres7">
insert into mytable ( row1, row2 ) values ( 12, 'stuff' )
< /query>
< query platform="mysql">
insert into mytable ( row1, row2 ) values ( 12, 'different stuff' )
< /query>
< /sql>
< /schema>
< / pre >
< p > Create a new database using the appropriate tool for your platform.< br / >
Executing the following PHP code will create the a < i > mytable< / i > and < i > myindex< / i >
in the database and insert one row into < i > mytable< / i > if the platform is postgres or mysql.< / p >
< pre >
include_once('/path/to/adodb.inc.php');
include_once('/path/to/adodb-xmlschema.inc.php');
< font color = "#006600" > // To build the schema, start by creating a normal ADOdb connection:< / font >
$db->NewADOConnection( 'mysql' );
$db->Connect( ... );
< font color = "#006600" > // Create the schema object and build the query array.< / font >
$schema = new < b > adoSchema< / b > ( $db );
< font color = "#006600" > // Optionally, set a prefix for newly-created tables. In this example
// the prefix "myprefix_" will result in a table named "myprefix_tablename".< / font >
$schema->< b > SetPrefix< / b > ( 'myprefix_' );
< font color = "#006600" > // Build the SQL array< / font >
$schema->< b > ParseSchema< / b > ( 'schema.xml' );
< font color = "#006600" > // Execute the SQL on the database< / font >
$result = $schema->< b > ExecuteSchema< / b > ();
< font color = "#006600" > // Finally, clean up after the XML parser
// (PHP won't do this for you!)< / font >
$schema->< b > Destroy< / b > ();
< / pre >
< h3 > Using AXMLS in Your
Application< / h3 >
< p >
There are two steps involved in using
AXMLS in your application: first,
you must create a schema, or XML representation of your
database, and second, you must create the PHP code that will
parse and execute the schema.< / p >
< p > Let's begin with a schema that describes a typical, if simplistic
user management table for an application.< / p >
< pre class = "listing" > < pre >
< ?xml version=" 1.0" ?>
< schema version=" 0.2" >
< table name=" users" >
< desc> A typical users table for our application.< /desc>
< field name=" userId" type=" I" >
< descr> A unique ID assigned to each user.< /descr>
2003-10-19 21:05:23 +02:00
< KEY/>
< AUTOINCREMENT/>
< /field>
2004-03-15 23:17:52 +01:00
< field name=" userName" type=" C" size=" 16" > < NOTNULL/> < /field>
< index name=" userName" >
< descr> Put a unique index on the user name< /descr>
< col> userName< /col>
< UNIQUE/>
< /index>
2003-10-19 21:05:23 +02:00
< /table>
2004-03-15 23:17:52 +01:00
2003-10-19 21:05:23 +02:00
< sql>
2004-03-15 23:17:52 +01:00
< descr> Insert some data into the users table.< /descr>
< query> insert into users (userName) values ( 'admin' )< /query>
< query> insert into users (userName) values ( 'Joe' )< /query>
2003-10-19 21:05:23 +02:00
< /sql>
2004-03-15 23:17:52 +01:00
< /schema>
< / pre > < / pre >
< p > Let's take a detailed look at this schema.< / p >
< p > The opening < ?xml version=" 1.0" ?> tag is
required by XML. The < schema> tag
tells the parser that the enclosed markup defines an XML
schema. The version=" 0.2" attribute sets
< em > the version of the AXMLS DTD used by the XML
schema.< / em > < p > All versions of AXMLS prior
to version 1.0 have a schema version of " 0.1" . The current
schema version is " 0.2" .< / p > < / p >
< pre class = "listing" > < pre >
< ?xml version=" 1.0" ?>
< schema version=" 0.2" >
...
2003-10-19 21:05:23 +02:00
< /schema>
2004-03-15 23:17:52 +01:00
< / pre > < / pre >
< p > Next we define one or more tables. A table consists of a
fields (and other objects) enclosed by
< table> tags. The
name=" " attribute specifies the name of
the table that will be created in the database.< / p >
< pre class = "listing" > < pre >
< table name=" users" >
2003-10-19 21:05:23 +02:00
2004-03-15 23:17:52 +01:00
< desc> A typical users table for our application.< /desc>
< field name=" userId" type=" I" >
< descr> A unique ID assigned to each user.< /descr>
< KEY/>
< AUTOINCREMENT/>
< /field>
< field name=" userName" type=" C" size=" 16" > < NOTNULL/> < /field>
< /table>
< / pre > < / pre >
< p > This table is called " users" and has a description and
two fields. The description is optional, and is currently
only for your own information; it is not applied to the
database.< / p >
< p > The first < field> tag will create
a field named " userId" of type " I" , or integer. (See the
ADOdb Data Dictionary
documentation for a list of valid types.) This
< field> tag encloses two special
field options: < KEY/> , which
specifies this field as a primary key, and
< AUTOINCREMENT/> , which specifies
that the database engine should automatically fill this
field with the next available value when a new row is
inserted.< / p >
< p > The second < field> tag will create
a field named " userName" of type " C" , or character, and of
length 16 characters. The < NOTNULL/>
option specifies that this field does not allow
NULLs.< / p >
< p > There are two ways to add indexes to a table. The
simplest is to mark a field with the
< KEY/> option as described above; a
primary key is a unique index. The second and more powerful
method uses the < index> tags.< / p >
< pre class = "listing" > < pre >
< table name=" users" >
...
< index name=" userName" >
< descr> Put a unique index on the user name< /descr>
< col> userName< /col>
< UNIQUE/>
< /index>
< /table>
< / pre > < / pre >
< p > The < index> tag specifies that an
index should be created on the enclosing table. The
name=" " attribute provides the name of the
index that will be created in the database. The
description, as above, is for your information only. The
< col> tags list each column that
will be included in the index. Finally, the
< UNIQUE/> tag specifies that this
will be created as a unique index.< / p >
< p > Finally, AXMLS allows you to include arbitrary SQL that
will be applied to the database when the schema is
executed.< / p >
< pre class = "listing" > < pre >
< sql>
< descr> Insert some data into the users table.< /descr>
< query> insert into users (userName) values ( 'admin' )< /query>
< query> insert into users (userName) values ( 'Joe' )< /query>
< /sql>
< / pre > < / pre >
< p > The < sql> tag encloses any number
of SQL queries that you define for your own use.< / p >
< p > Now that we've defined an XML schema, you need to know how to
apply it to your database. Here's a simple PHP script that shows
how to load the schema.< / p >
< p > < pre class = "listing" > < pre >
< ?PHP
/* You must tell the script where to find the ADOdb and
* the AXMLS libraries.
*/
require( " path_to_adodb/adodb.inc.php" );
require( " path_to_adodb/adodb-xmlschema.inc.php" );
2003-10-19 21:05:23 +02:00
2004-03-15 23:17:52 +01:00
/* Configuration information. Define the schema filename,
* RDBMS platform (see the ADODB documentation for valid
* platform names), and database connection information here.
*/
$schemaFile = 'example.xml';
$platform = 'mysql';
$dbHost = 'localhost';
$dbName = 'database';
$dbUser = 'username';
$dbPassword = 'password';
2003-10-19 21:05:23 +02:00
2004-03-15 23:17:52 +01:00
/* Start by creating a normal ADODB connection.
*/
$db = ADONewConnection( $platform );
$db-> Connect( $dbHost, $dbUser, $dbPassword, $dbName );
2003-10-19 21:05:23 +02:00
2004-03-15 23:17:52 +01:00
/* Use the database connection to create a new adoSchema object.
*/
$schema = new adoSchema( $db );
2003-10-19 21:05:23 +02:00
2004-03-15 23:17:52 +01:00
/* Call ParseSchema() to build SQL from the XML schema file.
* Then call ExecuteSchema() to apply the resulting SQL to
* the database.
*/
$sql = $schema-> ParseSchema( $schemaFile );
$result = $schema-> ExecuteSchema();
?>
< / pre > < / pre > < / p >
< p > Let's look at each part of the example in turn. After you
manually create the database, there are three steps required to
load (or upgrade) your schema.< / p >
< p > First, create a normal ADOdb connection. The variables
and values here should be those required to connect to your
database.< / p >
< pre class = "listing" > < pre >
$db = ADONewConnection( 'mysql' );
$db-> Connect( 'host', 'user', 'password', 'database' );
< / pre > < / pre >
< p > Second, create the adoSchema object that load and
manipulate your schema. You must pass an ADOdb database
connection object in order to create the adoSchema
object.< / p >
< pre class = "listing" > < pre >
$schema = new adoSchema( $db );
< / pre > < / pre >
< p > Third, call ParseSchema() to parse the
schema and then ExecuteSchema() to apply
it to the database. You must pass
ParseSchema() the path and filename of
your schema file.< / p >
< pre class = "listing" > < pre >
$schema-> ParseSchema( $schemaFile );
$schema-> ExecuteSchema();
< / pre > < / pre >
< p > Execute the above code and then log into your database. If you've
done all this right, you should see your tables, indexes, and
SQL.< / p >
< p > You can find the source files for this tutorial in the
examples directory as
tutorial_shema.xml and
tutorial.php. See the class documentation for
a more detailed description of the adoSchema methods, including
methods and schema elements that are not described in this
tutorial.< / p >
2003-10-19 21:05:23 +02:00
< H3 > XML Schema Format:< / H3 >
2004-03-15 23:17:52 +01:00
< P > (See < a href = "xmlschema.dtd" > xmlschema.dtd< / a > for the full specification)< / P >
2003-10-19 21:05:23 +02:00
< PRE >
2004-03-15 23:17:52 +01:00
< ?xml version="1.0"?>
< schema version=" 0.2" >
< table name="tablename" platform="platform1|platform2|...">
< descr> Optional description< /descr>
< field name="fieldname" type="datadict_type" size="size">
< KEY/>
< NOTNULL/>
< AUTOINCREMENT/>
< DEFAULT value="value"/>
< /field>
< i > ... more fields< / i >
< index name="indexname" platform="platform1|platform2|...">
< descr> Optional description< /descr>
< col> fieldname< /col>
< i > ... more columns< / i >
< /index>
< i > ... more indexes< / i >
< /table>
< i > ... more tables< / i >
< sql platform="platform1|platform2|...">
< descr> Optional description< /descr>
< query platform="platform1|platform2|..."> SQL query< /query>
< i > ... more queries< / i >
< /sql>
< i > ... more SQL< / i >
2003-10-19 21:05:23 +02:00
< /schema>
2004-03-15 23:17:52 +01:00
< / pre >
< h3 > Upgrading< / h3 >
If your schema version is older, than XSLT is used to transform the schema to the newest version.
This means that if you are using an older XML schema format, you need to have the XSLT extension installed.
If you do not want to require your users to have the XSLT extension installed, make sure you
modify your XML schema to conform to the latest version.
< hr / >
2003-10-19 21:05:23 +02:00
2004-03-15 23:17:52 +01:00
< address > If you have any questions or comments, please email them to Richard at richtl#arscognita.com.
< / address >
2003-10-19 21:05:23 +02:00
< / body >
2004-03-15 23:17:52 +01:00
< / html >
