From sacadmin Mon Dec 10 09:17:09 2007 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id lBAHH9Ud002587 for ; Mon, 10 Dec 2007 09:17:09 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id lBAHH8XJ016952 for <@sunmail2sca.sfbay.sun.com:lsarc@Sun.COM>; Mon, 10 Dec 2007 09:17:09 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JSU00M3ZG0JP900@nwk-avmta-2.sfbay.sun.com> for lsarc@Sun.COM (ORCPT lsarc@Sun.COM); Mon, 10 Dec 2007 09:17:07 -0800 (PST) Received: from dm-uk-02.uk.sun.com ([129.156.101.196]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JSU00JF3G0H5Y70@nwk-avmta-2.sfbay.sun.com> for lsarc@Sun.COM (ORCPT lsarc@Sun.COM); Mon, 10 Dec 2007 09:17:05 -0800 (PST) Received: from serinus.UK.Sun.COM (serinus.UK.Sun.COM [129.156.173.208]) by dm-uk-02.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id lBAHH3L2014225; Mon, 10 Dec 2007 17:17:03 +0000 (GMT) Received: from [129.148.226.14] (sr1-unsh01-04.East.Sun.COM [129.148.226.14]) by serinus.UK.Sun.COM (8.13.7+Sun/8.13.7/CTE 3.0) with ESMTP id lBAHH24u020694; Mon, 10 Dec 2007 17:17:02 +0000 (GMT) Date: Mon, 10 Dec 2007 12:17:02 -0500 From: Jim Gates Subject: LSARC 2007/684 - unixODBC - Provide ODBC Driver Manager for OpenSolaris - fast-track To: lsarc@sun.com Cc: =?ISO-8859-1?Q?Magne_M=E6hre?= , Sriram.Natarajan@sun.com Message-id: <475D748E.8070403@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_WaDF+3Uds/Tm0KwU2gv0jQ)" X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 User-Agent: Mozilla/5.0 (X11; U; SunOS sun4v; en-US; rv:1.7) Gecko/20070606 Status: RO Content-Length: 4236 This is a multi-part message in MIME format. --Boundary_(ID_WaDF+3Uds/Tm0KwU2gv0jQ) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT I am sponsoring this fast-track on behalf of Magne Maehre. The timer expires 12/18/07. Attached is a copy of the proposal, which can also be found in the case directory. --Boundary_(ID_WaDF+3Uds/Tm0KwU2gv0jQ) Content-type: text/plain; name=unixODBC_one_pager.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=unixODBC_one_pager.txt Template Version: @(#)onepager.txt 1.31 07/08/08 SMI This information is Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: unixODBC - Provide ODBC Driver Manager for OpenSolaris 1.2. Name of Document Author/Supplier: Magne Mahre 1.3. Date of This Document: 12/06/2007 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Database 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Heidi Bergh-Hoff 1.4.4. The name of your business unit: DBTG 1.5. Email Aliases: 1.5.1. Responsible Manager: Masood.Mortazavi@sun.com 1.5.2. Responsible Engineer: Sriram.Natarajan@Sun.COM 1.5.3. Marketing Manager: Rebecca.Hansen@sun.com 1.5.4. Interest List: databases-discuss@opensolaris.org postgresql-techteam@sun.com sun-postgres-pteam@sun.com 2. Project Summary 2.1. Project Description: Provide unixODBC, the prominent OSS ODBC driver manager for OpenSolaris. 4. Technical Description: 4.1. Details: unixODBC is an open source ODBC driver manager. The driver manager enables use of ODBC database drivers for applications. This project will build and provide the driver manager itself. The unixODBC team also provides a GUI tool for configuration, but this tool will not be included at this time because of dependencies and potential licensing issues. User configuration is via configuration files. See: http://www.unixodbc.org/ 4.5. Interfaces: /usr/bin/dltest /usr/bin/isql /usr/bin/iusql /usr/bin/odbc_config /usr/bin/odbcinst /etc/odbc.ini /etc/odbcinst.ini /usr/include/autotest.h /usr/include/odbcinst.h /usr/include/odbcinstext.h /usr/include/sql.h /usr/include/sqlext.h /usr/include/sqltypes.h /usr/include/sqlucode.h /usr/include/unixodbc_conf.h /usr/include/uodbc_extras.h /usr/include/uodbc_stats.h /usr/lib/libboundparam.so [LINK] /usr/lib/libboundparam.so.1 [LINK] /usr/lib/libboundparam.so.1.0.0 /usr/lib/libgtrtst.so [LINK] /usr/lib/libgtrtst.so.1 [LINK] /usr/lib/libgtrtst.so.1.0.0 /usr/lib/libodbc.so [LINK] /usr/lib/libodbc.so.1 [LINK] /usr/lib/libodbc.so.1.0.0 /usr/lib/libodbccr.so [LINK] /usr/lib/libodbccr.so.1 [LINK] /usr/lib/libodbccr.so.1.0.0 /usr/lib/libodbcinst.so [LINK] /usr/lib/libodbcinst.so.1 [LINK] /usr/lib/libodbcinst.so.1.0.0 The community has discussed whether the tools should be put in a /usr/bin/unixodbc directory, and the header files in a /usr/include/odbc directory to reduce clutter. There is, in particular, a potential issue with the 'isql' tool since this is a fairly generic name used by other database vendors. It should be noted that most, if not all, Linux distributions have the tools and support files located as in the proposal above. We request that ARC should consider whether installation /usr/bin/unixodbc and/or /usr/include/odbc will be better for the OpenSolaris product(s) as a whole. 5. Reference Documents: ISO/IEC 9075-3:2003 6. Resources and Schedule: 6.1. Projected Availability: Q3FY08 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: SFWNV 6.5. ARC review type: Fasttrack --Boundary_(ID_WaDF+3Uds/Tm0KwU2gv0jQ)-- From sacadmin Mon Dec 10 15:25:33 2007 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id lBANPX1E009244 for ; Mon, 10 Dec 2007 15:25:33 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id lBANI0BA024426; Mon, 10 Dec 2007 15:18:00 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JSU00L03WPZ5W00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 10 Dec 2007 15:17:59 -0800 (PST) Received: from buye.red.iplanet.com ([192.18.65.224]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JSU0087UWPYA1F0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 10 Dec 2007 15:17:58 -0800 (PST) Received: from buye.red.iplanet.com (localhost [127.0.0.1]) by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id lBANHwgO024550; Mon, 10 Dec 2007 15:17:58 -0800 (PST) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id lBANHwoc024549; Mon, 10 Dec 2007 15:17:58 -0800 (PST) Date: Mon, 10 Dec 2007 15:17:58 -0800 From: Jyri Virkki Subject: Re: LSARC 2007/684 - unixODBC - Provide ODBC Driver Manager for OpenSolaris - fast-track In-reply-to: <475D748E.8070403@Sun.COM> To: Jim Gates Cc: lsarc@sun.com, Magne.Mahre@sun.com, Sriram.Natarajan@sun.com Message-id: <20071210231758.GB24518@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.2.0.264296 References: <475D748E.8070403@Sun.COM> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 332 Jim Gates wrote: > > I am sponsoring this fast-track on behalf of Magne Maehre. The timer > expires 12/18/07. Attached is a copy of the proposal, which can also be > found in the case directory. The IAM file lists the case as open, shouldn't it be sent to lsarc-ext? -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From sacadmin Mon Dec 10 18:28:26 2007 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id lBB2SPMM020210 for ; Mon, 10 Dec 2007 18:28:25 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id lBB2SIpT010879; Tue, 11 Dec 2007 02:28:20 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JSV0020T5J6SX00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 10 Dec 2007 18:28:18 -0800 (PST) Received: from buye.red.iplanet.com ([192.18.65.224]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JSV004RY5J2KF60@nwk-avmta-1.sfbay.Sun.COM>; Mon, 10 Dec 2007 18:28:15 -0800 (PST) Received: from buye.red.iplanet.com (localhost [127.0.0.1]) by buye.red.iplanet.com (8.13.7+Sun/8.13.7) with ESMTP id lBB2SEb4025037; Mon, 10 Dec 2007 18:28:14 -0800 (PST) Received: (from jyri@localhost) by buye.red.iplanet.com (8.13.7+Sun/8.13.7/Submit) id lBB2SEjJ025036; Mon, 10 Dec 2007 18:28:14 -0800 (PST) Date: Mon, 10 Dec 2007 18:28:14 -0800 From: Jyri Virkki Subject: Re: LSARC 2007/684 - unixODBC - Provide ODBC Driver Manager for OpenSolaris - fast-track In-reply-to: <475D748E.8070403@Sun.COM> To: Jim Gates Cc: lsarc@sun.com, Magne.Mahre@sun.com, Sriram.Natarajan@sun.com Message-id: <20071211022814.GK24518@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.2.0.264296 References: <475D748E.8070403@Sun.COM> User-Agent: Mutt/1.5.11 Status: RO Content-Length: 829 Jim Gates wrote: > > 1.1. Project/Component Working Name: > > unixODBC - Provide ODBC Driver Manager for OpenSolaris The doc doesn't document the interface stability of any of its exported interfaces. Please add that. On a related note, it should say something about the expected stability of the upstream community. Can we expect these APIs to be stable or will they break on every x.y.z release or somewhere in between? What's the community policy, if there is one, and/or the historical track record? Are all the exported interfaces equally [un]stable or are some more recommended than others? Which version is being integrated by this project? Also, there's no imported interface table. Maybe it doesn't import anything, but wanted to be sure. -- Jyri J. Virkki - jyri.virkki@sun.com - Sun Microsystems From sacadmin Thu Dec 13 13:59:50 2007 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id lBDLxnCa020744 for ; Thu, 13 Dec 2007 13:59:49 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id lBDLxlnF003445 for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Thu, 13 Dec 2007 14:59:49 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JT00060TD3PKV00@nwk-avmta-1.sfbay.Sun.COM> for lsarc@sun.com (ORCPT lsarc@sun.com); Thu, 13 Dec 2007 13:59:49 -0800 (PST) Received: from sfbaymail1sca.SFBay.Sun.COM ([129.145.154.35]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JT0000NVD3LFQ60@nwk-avmta-1.sfbay.Sun.COM> for lsarc@sun.com (ORCPT lsarc@sun.com); Thu, 13 Dec 2007 13:59:45 -0800 (PST) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id lBDLxgr5013644; Thu, 13 Dec 2007 13:59:42 -0800 (PST) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id lBDLxgcB008481; Thu, 13 Dec 2007 13:59:42 -0800 (PST) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id lBDLxgXh008480; Thu, 13 Dec 2007 13:59:42 -0800 (PST) Date: Thu, 13 Dec 2007 13:59:42 -0800 From: Danek Duvall Subject: Re: LSARC 2007/684 - unixODBC - Provide ODBC Driver Manager for OpenSolaris - fast-track In-reply-to: <475D748E.8070403@Sun.COM> To: Jim Gates Cc: lsarc@sun.com, Magne M?hre , Sriram.Natarajan@sun.com Message-id: <20071213215942.GF7450@zruty.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.2.0.264296 References: <475D748E.8070403@Sun.COM> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 1226 On Mon, Dec 10, 2007 at 12:17:02PM -0500, Jim Gates wrote: > 4.5. Interfaces: > > /usr/bin/dltest > /usr/bin/isql > /usr/bin/iusql > /usr/bin/odbc_config > /usr/bin/odbcinst Are there man pages for these commands that might describe a bit better what they do? It's hard to evaluate whether they really belong in /usr/bin if we don't know what they actually are. :) In the case of isql, can it act in the stead of, say, the Oracle isql command (perhaps with an appropriate plugin)? You talk about individual database drivers. Where would these go? > /usr/include/autotest.h > /usr/include/odbcinst.h > /usr/include/odbcinstext.h > /usr/include/sql.h > /usr/include/sqlext.h > /usr/include/sqltypes.h > /usr/include/sqlucode.h > /usr/include/unixodbc_conf.h > /usr/include/uodbc_extras.h > /usr/include/uodbc_stats.h My feel for these is to put them in their own directory, but I don't know how common those particular names are, so maybe it wouldn't be a big deal, but it's usually a bit easier to sequester header files than commands, or even libraries. You don't mention stability levels for any of these interfaces. Please provide. Thanks, Danek From sacadmin Fri Dec 14 02:18:23 2007 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id lBEAINaS004935 for ; Fri, 14 Dec 2007 02:18:23 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id lBEAIL4O008479 for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Fri, 14 Dec 2007 02:18:23 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JT10060LBAKXE00@brm-avmta-1.central.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 14 Dec 2007 03:18:20 -0700 (MST) Received: from gmp-eb-mail-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JT100K3DBAIYMA0@brm-avmta-1.central.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 14 Dec 2007 03:18:18 -0700 (MST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id lBEAIH3M006887 for ; Fri, 14 Dec 2007 10:18:17 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JT100501AI11100@fe-emea-09.sun.com> (original mail from Magne.Mahre@Sun.COM) for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 14 Dec 2007 10:18:17 +0000 (GMT) Received: from [129.159.112.248] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JT1006JDBAG4780@fe-emea-09.sun.com>; Fri, 14 Dec 2007 10:18:17 +0000 (GMT) Date: Fri, 14 Dec 2007 11:18:16 +0100 From: =?UTF-8?B?TWFnbmUgTcOmaHJl?= Subject: Re: LSARC 2007/684 - unixODBC - Provide ODBC Driver Manager for OpenSolaris - fast-track In-reply-to: <20071213215942.GF7450@zruty.sfbay.sun.com> Sender: Magne.Mahre@sun.com To: Danek Duvall Cc: Jim Gates , lsarc@sun.com, Sriram.Natarajan@sun.com Message-id: <47625868.1020706@sun.com> Organization: Sun Microsystems Inc. MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7BIT X-PMX-Version: 5.2.0.264296 References: <475D748E.8070403@Sun.COM> <20071213215942.GF7450@zruty.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.9 (X11/20071119) Status: RO Content-Length: 2601 Danek Duvall wrote: > On Mon, Dec 10, 2007 at 12:17:02PM -0500, Jim Gates wrote: > >> 4.5. Interfaces: >> >> /usr/bin/dltest >> /usr/bin/isql >> /usr/bin/iusql >> /usr/bin/odbc_config >> /usr/bin/odbcinst > > Are there man pages for these commands that might describe a bit better > what they do? It's hard to evaluate whether they really belong in /usr/bin > if we don't know what they actually are. :) It seems like the community doesn't provide man pages for any of these. dltest: utility to check whether a symbol is defined in a shared library isql: interactive sql tool iusql: unicode enabled interactive sql tool odbc_config: developer tool that can be used from Makefiles to determine where the includes and libs are installed odbcinst: driver installation utility > In the case of isql, can it act in the stead of, say, the Oracle isql > command (perhaps with an appropriate plugin)? IIRC how the Oracle tool works, this is more rudimentary. It is a simple interactive tool that uses any of the installed drivers to connect to the corresponding database. It's mostly used for testing if ODBC is working properly, I think. None of these tools are strictly necessary for the operation of the driver manager. > You talk about individual database drivers. Where would these go? We don't provide any drivers as of yet, but the location of these drivers can be anywhere as it is pointed to by the odbcinst.ini file For PostgreSQL, the driver will be located within the PG sub-tree (/usr/postgres/ ) >> /usr/include/autotest.h >> /usr/include/odbcinst.h >> /usr/include/odbcinstext.h >> /usr/include/sql.h >> /usr/include/sqlext.h >> /usr/include/sqltypes.h >> /usr/include/sqlucode.h >> /usr/include/unixodbc_conf.h >> /usr/include/uodbc_extras.h >> /usr/include/uodbc_stats.h > > My feel for these is to put them in their own directory, but I don't know > how common those particular names are, so maybe it wouldn't be a big deal, > but it's usually a bit easier to sequester header files than commands, or > even libraries. Since we have odbc_config, I guess they can be installed in a separate directory, and I will suggest /usr/include/odbc/ . > You don't mention stability levels for any of these interfaces. Please > provide. Since Sun doesn't have control over these, but it implements an ISO standard, I think Uncommitted will be the correct level for the provided API (header files). For the tools, Volatile seems more appropriate. I will update the document. --Magne From sacadmin Fri Dec 14 15:13:43 2007 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id lBENDg2p017120 for ; Fri, 14 Dec 2007 15:13:42 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id lBENDXBd002659 for <@sunmail2sca.sfbay.sun.com:lsarc@Sun.COM>; Sat, 15 Dec 2007 07:13:41 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JT200A01B6QQI00@nwk-avmta-1.sfbay.Sun.COM> for lsarc@Sun.COM (ORCPT lsarc@Sun.COM); Fri, 14 Dec 2007 15:13:38 -0800 (PST) Received: from sfbaymail2sca.sfbay.sun.com ([129.145.155.42]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JT2000F2B6Q05B0@nwk-avmta-1.sfbay.Sun.COM> for lsarc@Sun.COM (ORCPT lsarc@Sun.COM); Fri, 14 Dec 2007 15:13:38 -0800 (PST) Received: from zruty.sfbay.sun.com (zruty.SFBay.Sun.COM [129.146.168.40]) by sfbaymail2sca.sfbay.sun.com (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id lBENDYIL015443; Fri, 14 Dec 2007 15:13:34 -0800 (PST) Received: from zruty.sfbay.sun.com (localhost [127.0.0.1]) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1) with ESMTP id lBENDYAI002429; Fri, 14 Dec 2007 15:13:34 -0800 (PST) Received: (from dduvall@localhost) by zruty.sfbay.sun.com (8.14.1+Sun/8.14.1/Submit) id lBENDYdc002428; Fri, 14 Dec 2007 15:13:34 -0800 (PST) Date: Fri, 14 Dec 2007 15:13:34 -0800 From: Danek Duvall Subject: Re: LSARC 2007/684 - unixODBC - Provide ODBC Driver Manager for OpenSolaris - fast-track In-reply-to: <47625868.1020706@sun.com> To: Magne M?hre Cc: Jim Gates , lsarc@sun.com, Sriram.Natarajan@sun.com Message-id: <20071214231334.GW17670@zruty.sfbay.sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.2.0.264296 References: <475D748E.8070403@Sun.COM> <20071213215942.GF7450@zruty.sfbay.sun.com> <47625868.1020706@sun.com> User-Agent: Mutt/1.5.16 (2007-06-27) Status: RO Content-Length: 2385 On Fri, Dec 14, 2007 at 11:18:16AM +0100, Magne M?hre wrote: > It seems like the community doesn't provide man pages for any of these. Hrm. Would you be able to write some small man pages that gave some idea of what the utilities did? I'm sure the community wouldn't mind the contribution, either. :) There's little point in putting things on the system if you can't find out what they're for. > dltest: utility to check whether a symbol is defined in a shared library > isql: interactive sql tool > iusql: unicode enabled interactive sql tool > odbc_config: developer tool that can be used from Makefiles to > determine where the includes and libs are installed > odbcinst: driver installation utility Wow, okay. I'm certainly not happy with all these in /usr/bin, but other than clutter, I can't think of a reason they can't be there. >> In the case of isql, can it act in the stead of, say, the Oracle isql >> command (perhaps with an appropriate plugin)? > > IIRC how the Oracle tool works, this is more rudimentary. It is a > simple interactive tool that uses any of the installed drivers to > connect to the corresponding database. It's mostly used for > testing if ODBC is working properly, I think. > > None of these tools are strictly necessary for the operation of > the driver manager. Okay. Not even odbcinst? >> You talk about individual database drivers. Where would these go? > > We don't provide any drivers as of yet, but the location of these > drivers can be anywhere as it is pointed to by the odbcinst.ini file > > For PostgreSQL, the driver will be located within the PG sub-tree > (/usr/postgres/ ) Then you're not recommending a directory where drivers for all DBs would live, but rather that they live in some directory defined by each DB? > Since we have odbc_config, I guess they can be installed in a separate > directory, and I will suggest /usr/include/odbc/ . That works for me. >> You don't mention stability levels for any of these interfaces. Please >> provide. > > Since Sun doesn't have control over these, but it implements an ISO > standard, I think Uncommitted will be the correct level for the > provided API (header files). For the tools, Volatile seems more > appropriate. Okay. That even gives us the ability to remove seemingly useless tools like dltest should the need ever arise. Danek From sacadmin Mon Dec 17 13:05:06 2007 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id lBHL55nV027397 for ; Mon, 17 Dec 2007 13:05:06 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id lBHL54Bs025503 for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Tue, 18 Dec 2007 05:05:04 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JT700D05P8EFA00@nwk-avmta-2.sfbay.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Mon, 17 Dec 2007 13:05:02 -0800 (PST) Received: from dm-uk-01.uk.sun.com ([129.156.101.115]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JT700ACCP8BMD40@nwk-avmta-2.sfbay.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Mon, 17 Dec 2007 13:05:00 -0800 (PST) Received: from serinus.UK.Sun.COM (serinus.UK.Sun.COM [129.156.173.208]) by dm-uk-01.uk.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id lBHL4tDb026412; Mon, 17 Dec 2007 21:04:55 +0000 (GMT) Received: from [192.168.1.101] (vpn-129-150-67-123.East.Sun.COM [129.150.67.123]) by serinus.UK.Sun.COM (8.13.7+Sun/8.13.7/CTE 3.0) with ESMTP id lBHL4hKN001397; Mon, 17 Dec 2007 21:04:47 +0000 (GMT) Date: Mon, 17 Dec 2007 16:04:19 -0500 From: James Gates Subject: Re: LSARC 2007/684 - unixODBC - Provide ODBC Driver Manager for OpenSolaris - fast-track In-reply-to: <20071214231334.GW17670@zruty.sfbay.sun.com> To: Danek Duvall Cc: Magne M?hre , lsarc@sun.com, Sriram.Natarajan@sun.com Message-id: <4766E453.9@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 References: <475D748E.8070403@Sun.COM> <20071213215942.GF7450@zruty.sfbay.sun.com> <47625868.1020706@sun.com> <20071214231334.GW17670@zruty.sfbay.sun.com> User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.13) Gecko/20060509 Status: RO Content-Length: 2740 Danek Duvall wrote: > On Fri, Dec 14, 2007 at 11:18:16AM +0100, Magne M?hre wrote: > > >>It seems like the community doesn't provide man pages for any of these. > > > Hrm. Would you be able to write some small man pages that gave some idea > of what the utilities did? I'm sure the community wouldn't mind the > contribution, either. :) There's little point in putting things on the > system if you can't find out what they're for. This is what we did for pgAdmin3 (the PostgreSQL GUI admin tool recently integrated). See LSARC/2006/644. Also see man pages pgadmin(1) & pgagent(1). I believe they're just a man/nroff version of the community web site's "about" page. > > >>dltest: utility to check whether a symbol is defined in a shared library >>isql: interactive sql tool >>iusql: unicode enabled interactive sql tool >>odbc_config: developer tool that can be used from Makefiles to >> determine where the includes and libs are installed >>odbcinst: driver installation utility > > > Wow, okay. I'm certainly not happy with all these in /usr/bin, but other > than clutter, I can't think of a reason they can't be there. > > >>>In the case of isql, can it act in the stead of, say, the Oracle isql >>>command (perhaps with an appropriate plugin)? >> >>IIRC how the Oracle tool works, this is more rudimentary. It is a >>simple interactive tool that uses any of the installed drivers to >>connect to the corresponding database. It's mostly used for >>testing if ODBC is working properly, I think. >> >>None of these tools are strictly necessary for the operation of >>the driver manager. > > > Okay. Not even odbcinst? > > >>>You talk about individual database drivers. Where would these go? >> >>We don't provide any drivers as of yet, but the location of these >>drivers can be anywhere as it is pointed to by the odbcinst.ini file >> >>For PostgreSQL, the driver will be located within the PG sub-tree >>(/usr/postgres/ ) > > > Then you're not recommending a directory where drivers for all DBs would > live, but rather that they live in some directory defined by each DB? > > >>Since we have odbc_config, I guess they can be installed in a separate >>directory, and I will suggest /usr/include/odbc/ . > > > That works for me. > > >>>You don't mention stability levels for any of these interfaces. Please >>>provide. >> >>Since Sun doesn't have control over these, but it implements an ISO >>standard, I think Uncommitted will be the correct level for the >>provided API (header files). For the tools, Volatile seems more >>appropriate. > > > Okay. That even gives us the ability to remove seemingly useless tools > like dltest should the need ever arise. > > Danek From sacadmin Wed Apr 15 07:14:08 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FEE8Ps019904 for ; Wed, 15 Apr 2009 07:14:08 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3FEE6UJ029002; Wed, 15 Apr 2009 07:14:07 -0700 (PDT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KI500M07BJIHW00@brm-avmta-1.central.sun.com>; Wed, 15 Apr 2009 08:14:06 -0600 (MDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KI500EASBJHY760@brm-avmta-1.central.sun.com>; Wed, 15 Apr 2009 08:14:05 -0600 (MDT) Received: from [10.7.251.44] (punchin-client-10-7-251-44.SFBay.Sun.COM [10.7.251.44]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n3FEE44X258047; Wed, 15 Apr 2009 07:14:04 -0700 (PDT) Date: Wed, 15 Apr 2009 10:17:57 -0400 From: Stefan Teleman Subject: LSARC 2007/684 - unixODBC To: lsarc@sun.com Cc: Norm Jacobs , Stefan Teleman Reply-to: stefan.teleman@sun.com Message-id: <49E5EC95.9010405@Sun.COM> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; charset=UTF-8; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.4 (X11/20070622) Status: RO Content-Length: 3742 Hi. LSARC/2007/684 and LSARC/2009/064 did not explicitly indicate that the corresponding 64-bit shared objects will be delivered in the Standard ${MACH64} locations, in addition to the 32-bit objects: /usr/lib/${MACH64}/* /usr/lib/${MACH64}/libboundparam.so.1.0.0 /usr/lib/${MACH64}/libesoobS.so.1.0.0 /usr/lib/${MACH64}/libgtrtst.so.1.0.0 /usr/lib/${MACH64}/libmimerS.so.1.0.0 /usr/lib/${MACH64}/libnn.so.1.0.0 /usr/lib/${MACH64}/libodbc.so.1.0.0 /usr/lib/${MACH64}/libodbccr.so.1.0.0 /usr/lib/${MACH64}/libodbcdrvcfg1S.so.1.0.0 /usr/lib/${MACH64}/libodbcdrvcfg2S.so.1.0.0 /usr/lib/${MACH64}/libodbcinst.so.1.0.0 /usr/lib/${MACH64}/libodbcminiS.so.1.0.0 /usr/lib/${MACH64}/libodbcmyS.so.1.0.0 /usr/lib/${MACH64}/libodbcnnS.so.1.0.0 /usr/lib/${MACH64}/libodbcpsql.so.1.0.0 /usr/lib/${MACH64}/libodbcpsql.so.2.0.0 /usr/lib/${MACH64}/libodbcpsqlS.so.1.0.0 /usr/lib/${MACH64}/libodbctxtS.so.1.0.0 /usr/lib/${MACH64}/liboplodbcS.so.1.0.0 /usr/lib/${MACH64}/liboraodbcS.so.1.0.0 /usr/lib/${MACH64}/libsapdbS.so.1.0.0 /usr/lib/${MACH64}/libtdsS.so.1.0.0 /usr/lib/${MACH64}/libtemplate.so.1.0.0 /usr/lib/${MACH64}/libboundparam.so.1 -> libboundparam.so.1.0.0 /usr/lib/${MACH64}/libboundparam.so -> libboundparam.so.1.0.0 /usr/lib/${MACH64}/libesoobS.so.1 -> libesoobS.so.1.0.0 /usr/lib/${MACH64}/libesoobS.so -> libesoobS.so.1.0.0 /usr/lib/${MACH64}/libgtrtst.so.1 -> libgtrtst.so.1.0.0 /usr/lib/${MACH64}/libgtrtst.so -> libgtrtst.so.1.0.0 /usr/lib/${MACH64}/libmimerS.so.1 -> libmimerS.so.1.0.0 /usr/lib/${MACH64}/libmimerS.so -> libmimerS.so.1.0.0 /usr/lib/${MACH64}/libnn.so.1 -> libnn.so.1.0.0 /usr/lib/${MACH64}/libnn.so -> libnn.so.1.0.0 /usr/lib/${MACH64}/libodbc.so.1 -> libodbc.so.1.0.0 /usr/lib/${MACH64}/libodbc.so -> libodbc.so.1.0.0 /usr/lib/${MACH64}/libodbccr.so.1 -> libodbccr.so.1.0.0 /usr/lib/${MACH64}/libodbccr.so -> libodbccr.so.1.0.0 /usr/lib/${MACH64}/libodbcdrvcfg1S.so.1 -> libodbcdrvcfg1S.so.1.0.0 /usr/lib/${MACH64}/libodbcdrvcfg1S.so -> libodbcdrvcfg1S.so.1.0.0 /usr/lib/${MACH64}/libodbcdrvcfg2S.so.1 -> libodbcdrvcfg2S.so.1.0.0 /usr/lib/${MACH64}/libodbcdrvcfg2S.so -> libodbcdrvcfg2S.so.1.0.0 /usr/lib/${MACH64}/libodbcinst.so.1 -> libodbcinst.so.1.0.0 /usr/lib/${MACH64}/libodbcinst.so -> libodbcinst.so.1.0.0 /usr/lib/${MACH64}/libodbcminiS.so.1 -> libodbcminiS.so.1.0.0 /usr/lib/${MACH64}/libodbcminiS.so -> libodbcminiS.so.1.0.0 /usr/lib/${MACH64}/libodbcmyS.so.1 -> libodbcmyS.so.1.0.0 /usr/lib/${MACH64}/libodbcmyS.so -> libodbcmyS.so.1.0.0 /usr/lib/${MACH64}/libodbcnnS.so.1 -> libodbcnnS.so.1.0.0 /usr/lib/${MACH64}/libodbcnnS.so -> libodbcnnS.so.1.0.0 /usr/lib/${MACH64}/libodbcpsql.so.1 -> libodbcpsql.so.1.0.0 /usr/lib/${MACH64}/libodbcpsql.so.2 -> libodbcpsql.so.2.0.0 /usr/lib/${MACH64}/libodbcpsql.so -> libodbcpsql.so.2.0.0 /usr/lib/${MACH64}/libodbcpsqlS.so.1 -> libodbcpsqlS.so.1.0.0 /usr/lib/${MACH64}/libodbcpsqlS.so -> libodbcpsqlS.so.1.0.0 /usr/lib/${MACH64}/libodbctxtS.so.1 -> libodbctxtS.so.1.0.0 /usr/lib/${MACH64}/libodbctxtS.so -> libodbctxtS.so.1.0.0 /usr/lib/${MACH64}/liboplodbcS.so.1 -> liboplodbcS.so.1.0.0 /usr/lib/${MACH64}/liboplodbcS.so -> liboplodbcS.so.1.0.0 /usr/lib/${MACH64}/liboraodbcS.so.1 -> liboraodbcS.so.1.0.0 /usr/lib/${MACH64}/liboraodbcS.so -> liboraodbcS.so.1.0.0 /usr/lib/${MACH64}/libsapdbS.so.1 -> libsapdbS.so.1.0.0 /usr/lib/${MACH64}/libsapdbS.so -> libsapdbS.so.1.0.0 /usr/lib/${MACH64}/libtdsS.so.1 -> libtdsS.so.1.0.0 /usr/lib/${MACH64}/libtdsS.so -> libtdsS.so.1.0.0 /usr/lib/${MACH64}/libtemplate.so.1 -> libtemplate.so.1.0.0 /usr/lib/${MACH64}/libtemplate.so -> libtemplate.so.1.0.0 The addition of these 64-bit shared objects does not cause interface stability changes. --Stefan -- Stefan Teleman Sun Microsystems, Inc. stefan.teleman@Sun.COM