Because they point to Web methods, Web Services proxy tables are of type procedure and are subject to all restrictions for this type:
Commands – You cannot issue a delete, update, or insert command against a table of type procedure, nor can you issue a create index, truncate table, or alter table command.
Joins – A Web Services proxy table can only be joined with one other table, and that table cannot be another Web Services proxy table.
Queries – Column names beginning with underscore ('_') are used to specify parameters, which are not part of the result set for the remote procedure. These columns are referred to as parameter columns and must be in the where clause of a select statement.
For a complete description of the restrictions for procedure tables, see the Component Integration Services User’s Guide.
A proxy table with the same name as a Web Services proxy table generated through execution of the add option of sp_webservices may be erroneously designated as a Web Services proxy table. Joins are processed for Web Services proxy tables differently than joins for regular proxy tables.
Confine Web Services proxy tables to a unique database.
The reserved word or is not supported in the where clause for a query involving Web Services proxy tables. This may result in errors for queries that are translated internally into queries that use the reserved word or. For example, the following query selects from the Web Services proxy table testint:
select * from testint where _in0 in (1, 2)
This query is translated internally into the following:
select * from testint where _in0 = 1 or _in0 = 2
Because the internal translation uses the reserved word or, the user-submitted query results in an error.
Alter the query so that its internal translation does not use the reserved word or. For example, the user-submitted query just described can be altered with the use of temporary tables:
create table a (col int) insert into a values (1) insert into a values (2) select * from testint where _in0 in (select col from a)
| Copyright © 2004. Sybase Inc. All rights reserved. |
|
|
