For odbc Connect(), koppur is not used. Place dsn in 1st parameter. ----- (db2): select versionnumber from sysibm.sysversions ----- ----- (db2): CREATE TABLE vcd_CoversAllowedOnMediatypes ( cover_type_id INTEGER(10) NOT NULL, media_type_id INTEGER(10) NOT NULL ) -----
Warning: odbc_exec() [function.odbc-exec]: SQL error: [IBM][CLI Driver][DB2/NT] SQL0104N An unexpected token "INTEGER" was found following "YPES ( cover_type_id". Expected tokens may include: "DATALINK". SQLSTATE=42601 , SQL state 42601 in SQLExecDirect in c:\wwwroot\VCD5\classes\adodb\drivers\adodb-odbc.inc.php on line 526
42601: [IBM][CLI Driver][DB2/NT] SQL0104N An unexpected token "INTEGER" was found following "YPES ( cover_type_id". Expected tokens may include: "DATALINK". SQLSTATE=42601
ADODB_DB2._Execute(CREATE TABLE vcd_CoversAllowedOnMediatypes (
cover_type_id ..., false) % line 833, file: adodb.inc.php
ADODB_DB2.Execute(CREATE TABLE vcd_CoversAllowedOnMediatypes (
cover_type_id ...) % line 263, file: adodb-datadict.inc.php
ADODB2_db2.ExecuteSQLArray(Array[126], false) % line 1558, file: adodb-xmlschema.inc.php
adoSchema.ExecuteSchema(null, false) % line 630, file: installer.php
installer.installDB() % line 231, file: installer.php
Same schema works great on mysql and mssql ..
any ideas ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This appears to be a problem with your connection. I have no problem using xmlschema with DB2. Which version of adodb are you using, as I have submitted some patches to the db2 driver related to xmlschema which appear in adodb 4.52
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here's the error output ..
For odbc Connect(), koppur is not used. Place dsn in 1st parameter. ----- (db2): select versionnumber from sysibm.sysversions ----- ----- (db2): CREATE TABLE vcd_CoversAllowedOnMediatypes ( cover_type_id INTEGER(10) NOT NULL, media_type_id INTEGER(10) NOT NULL ) -----
Warning: odbc_exec() [function.odbc-exec]: SQL error: [IBM][CLI Driver][DB2/NT] SQL0104N An unexpected token "INTEGER" was found following "YPES ( cover_type_id". Expected tokens may include: "DATALINK". SQLSTATE=42601 , SQL state 42601 in SQLExecDirect in c:\wwwroot\VCD5\classes\adodb\drivers\adodb-odbc.inc.php on line 526
42601: [IBM][CLI Driver][DB2/NT] SQL0104N An unexpected token "INTEGER" was found following "YPES ( cover_type_id". Expected tokens may include: "DATALINK". SQLSTATE=42601
ADODB_DB2._Execute(CREATE TABLE vcd_CoversAllowedOnMediatypes (
cover_type_id ..., false) % line 833, file: adodb.inc.php
ADODB_DB2.Execute(CREATE TABLE vcd_CoversAllowedOnMediatypes (
cover_type_id ...) % line 263, file: adodb-datadict.inc.php
ADODB2_db2.ExecuteSQLArray(Array[126], false) % line 1558, file: adodb-xmlschema.inc.php
adoSchema.ExecuteSchema(null, false) % line 630, file: installer.php
installer.installDB() % line 231, file: installer.php
Same schema works great on mysql and mssql ..
any ideas ?
This appears to be a problem with your connection. I have no problem using xmlschema with DB2. Which version of adodb are you using, as I have submitted some patches to the db2 driver related to xmlschema which appear in adodb 4.52