[DB-SIG] ANN: mxODBC Version 0.5

[M.-A. Lemburg]

Greg Stein (Exchange) wrote:
> I never got the time to update the spec and gave up. I suggested closing
> down the db-sig, but people pointed out that it still had more work to
> do. Namely, completing an update of the spec. So far, that task hasn't
> even appeared on the db-sig, let alone anybody stepping up to do it or
> contributing to an update in any way.

Ok, I'll give it a try. Are the exceptions Bill posted the only
things that were added since version 1.0 ?

> So... the best thing people can do to reduce confusion is stop working
> on code

... now that is a strange proposal :-)

> and spend some time on that spec. Another thing might be to
> break dbi out of the various distributions into its own module available
> from python.org.

But then you would take away the freedom of programmers wanting
to code their dbi-module in Python. With the new standard package
mechanism the naming confusion about the dbi module is reduced to a
minimum anyway. It just needs to be made clear that every
DB module needs to provide one.

BTW: I have added the alternative date/time format I proposed
earlier to mxODBC. To use it, you have to set a cursor variable
called 'datetimeformat' to (currently) either TIMEVALUE_DATETIMEFORMAT
(t_time-based values) or TUPLE_DATETIMEFORMAT (tuple-based values).
The tuples use these mappings:

	time		(hour,min,sec)
	date		(year,month,day)
	timestamp	(year,month,day,hour,minute,second,microsecond)

Are these names/mappings ok with you ?

-- 
Marc-Andre Lemburg


_______________
DB-SIG  - SIG on Tabular Databases in Python

send messages to: db-sig@python.org
administrivia to: db-sig-request@python.org
_______________