More information on jConnect stored procedures

[Pavel Karady]

Greetings everybody,

being new to the jConnect forum, can anybody direct me to documentation
explainig more about jConnect stored procedures (e.g. sp_jdbc_getindexinfo).

Thanks in advance
Pavel

[Pavel Karady]

"Pavel Karady" <firstname.lastname@nospam_kogerusa.com> wrote in message
news:479e3813$1@forums-1-dub...

For ASA 9.0.2.3420 database.

Pavel

[J]

On 28 Jan 2008 12:16:19 -0800, "Pavel Karady"
<firstname.lastname@nospam_kogerusa.com> wrote:

Not sure what you are looking for the source for the procedure is
available at <jconnect>/sp/sql_asa.sql

Just search for "sp_jdbc_getindexinfo".

Jay

[Pavel Karady]

"J" <jtotall...@sbcglobal.net> wrote in message
news:479f5832...@forums.sybase.com...

I'm looking for more information on the procedures generally - what they do
and what are they intended for, how they work, why they exist, what uses
them - not by self-investigating the source code.

Thanks.
Pavel

[J]

On 29 Jan 2008 10:00:03 -0800, "Pavel Karady"
<firstname.lastname@nospam_kogerusa.com> wrote:

The stored procedures are used by jConnect in some cases to
materialize results that the JDBC specs might require.

A simple example is <Connection>.setCatalog().
Since the DBMS has a facility to make to this "use database" it makes
sense to build on current function vs inventing some entirely new
semantic for the operation.

You can find a table spt_mda that will map getCatalog/setCatalog into
commands the DBMS understands.

insert dbo.spt_mda values ('SET_CATALOG', 3, 'use ?', 1, 7, 0, -1)
go
insert dbo.spt_mda values ('GET_CATALOG', 2, 'select db_name()', 1, 7,
0, -1)
go

More complicated MetaData requests may require whole stored procedures
devoted to their implementations.

A network trace with Ribo or some server tracing and knowledge of JDBC
api calls can show some implementations also. Tracing the MetaData
objects can reveal much of what goes on without particular knowledge
of the underlying implementations.

Jay