• 丰搜首页
• 文档中心
• 视频中心
• 丰搜贴吧
• 问题集锦
• 更多功能

选择显示字体大小

• 最大
• 较大
• 标准

在pb中控制db2表清单的内容

document:

　　powerbuilder offers several options for controlling the table list that appears in the database and datawindow painters. one or more of these options can significantly improve performance as well as 'hide' tables that are not of interest to a development team. this document addresses such techniques as they apply to powerbuilder's native interfaces to the mdi gateway, sybase.net gateway, directconnect server, and ibm drda databases (for 16-bit powerbuilder) as well as to odbc connections via ibm's client application enabler (cae) odbc driver.

　　depending upon the database interface used, there are several options available; they fall into the following general categories:

1. powerbuilder connection parameter (dbparm) settings,
2. powerbuilder's odbc ini file settings,
3. driver-specific options, and
4. powerbuilder development environment settings.

　　the following settings in the powerbuilder database profile affect what tables are displayed in the table list. in powerbuilder 6.0 and later, these settings can be found in the various tabs of the database profile painter; prior to version 6.0, these settings were placed in the dbparm string directly (below, the dbparm option name follows the tabbed dialog edit label in each section heading).

　　the examples that follow reflect setting these options as part of a dbparm. when using powerbuilder 6.0 or later, specify the identical syntax, with the exception of the leading and trailing quotation marks, in the appropriate edit field on the tabbed dialog. further documentation for these parameters can be found in the connecting to your database reference or in powerbuilder on-line help.

　　1.1 group authorization id/groupid (ibm drda and mdi gateway).

　　n.b. the pbmdi native driver is no longer available beginning with powerbuilder 7.0. additionally, the mdi gateway has reached its end-of-life as a product supported by sybase. customers should be migrating (or have migrated) to the directconnect server and use the pbdir native driver for powerbuilder connectivity. pbmdi can be used as an interim solution for connectivity via the directconnect db2 access service as long as the directconnect access service is configured to run in 'gateway compatible' mode.

　　n.b. the pbibm interface is available in 16-bit only due to the underlying ibm cae requirements. additionally, this interface is based on extremely old technology that is no longer supported by ibm. customers that have connected via this means in the past should have already changed client connectivity to other mechanisms, such as ibm's cae odbc driver.

　　by default the db2 tables that are displayed in the table list are those for which the user has select privilege. using this parameter causes tables that have select privilege granted to the specified group id (in addition to the user id and public) to be included in the table list. for example, a user who logs on with a user id of 'user001' and sets the dbparm groupid='group001' will cause the following select statement from the db2 system tables to be generated:

select distinct sysibm.systabauth.tcreator, sysibm.systabauth.ttname,
sysibm.systables.type
from sysibm.systabauth, sysibm.systables
where (sysibm.systabauth.ttname = sysibm.systables.name
and sysibm.systabauth.tcreator = sysibm.systables.creator
and (sysibm.systabauth.grantee = 'user001' or
sysibm.systabauth.grantee = 'group001' or
sysibm.systabauth.grantee = 'public' or
sysibm.systabauth.grantee = 'public' )
and (sysibm.systabauth.selectauth = 'g' or
sysibm.systabauth.selectauth = 'y'))