[DB-SIG] Next Version (was: Preparing statement API)

M.-A. Lemburg mal@lemburg.com
Sat, 29 Jan 2000 11:34:25 +0100

alexander smishlajev wrote:
> "M.-A. Lemburg" wrote:
> >
> > BTW, are there any other things which should be done for the
> > next version ?
> it would be helpful if db drivers could implement methods
> returning:
> - list of available (configured) data sources.

This can only be done for database manager, e.g. the ODBC
managers in Windows, iODBC and unixODBC. mxODBC will have
support for this in a future version.

> - list of database users: logon name, groups/roles
> - list of user groups (roles): name, members

Don't know where you would get these infos... you normally
have to have admin priviledges to even look at those sys tables.
An abstraction layer could query the sys tables directly, BTW.

> - list of database objects: owner (schema), name, type (table,
> view, alias/synonym, procedure etc.), temporary object flag,
> server-specific info and maybe permission list?  synonyms must
> point to corresponding object.

Don't know how other DBs implement this, but mxODBC has the
catalog methods for these things.
> such information is available at almost any db server, but each of
> them has own ways to obtain it.
> and...  in api spec v2.0 i cannot find anything about writing
> blobs to database.  am i missing something?

See the type object section: blobs should be wrapped into
Binary(string) objects and then passed to the .executeXXX()
methods as parameter. On output you will see a column type
equal to the BINARY type object in the cursor description.

Marc-Andre Lemburg
Business:                                      http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/